Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ae3690a7b22fa3c4c9263ed28527a0811f1a0592aa8a8871e50f690a2763cdd8

Tx prefix hash: 8d04511e0626d519526e04f9d8ceb8c67eb96c83a29f2e81ba09fb0700697a70
Tx public key: 6d0962a5aa2e4630d85223c5d0d190f3cf289795d2aaf29be8f2361f1a6c8da4
Timestamp: 1740816618 Timestamp [UCT]: 2025-03-01 08:10:18 Age [y:d:h:m:s]: 00:337:06:06:14
Block: 1229672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238709 RingCT/type: yes/0
Extra: 016d0962a5aa2e4630d85223c5d0d190f3cf289795d2aaf29be8f2361f1a6c8da4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22cedff0c163feaf86eaa66df93ae433994c5b9fd6c21634c3da732e0856a79e 0.600000000000 1716559 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1229682, "vin": [ { "gen": { "height": 1229672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22cedff0c163feaf86eaa66df93ae433994c5b9fd6c21634c3da732e0856a79e" } } ], "extra": [ 1, 109, 9, 98, 165, 170, 46, 70, 48, 216, 82, 35, 197, 208, 209, 144, 243, 207, 40, 151, 149, 210, 170, 242, 155, 232, 242, 54, 31, 26, 108, 141, 164, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8