Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709de8b4ff94d91cae7f23c87e38a00c0b4b757053e6b10923a1a94400992a21

Tx prefix hash: 005a2a9dfc9f4c1c6b930e52e03e5b46e800b803724cd73d6d8d6048d2409777
Tx public key: b1aa511dd830d7c5be35d81f7e083bc6a2bd2faa3e91482ad754f132c8a27fda
Timestamp: 1728190220 Timestamp [UCT]: 2024-10-06 04:50:20 Age [y:d:h:m:s]: 00:202:12:09:10
Block: 1125460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144549 RingCT/type: yes/0
Extra: 01b1aa511dd830d7c5be35d81f7e083bc6a2bd2faa3e91482ad754f132c8a27fda02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e07cf8f340a93ba88034d6a39643409e0934fbbad60c8a534ffc2c05b8ecdb 0.600000000000 1608209 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": 1125470, "vin": [ { "gen": { "height": 1125460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e07cf8f340a93ba88034d6a39643409e0934fbbad60c8a534ffc2c05b8ecdb" } } ], "extra": [ 1, 177, 170, 81, 29, 216, 48, 215, 197, 190, 53, 216, 31, 126, 8, 59, 198, 162, 189, 47, 170, 62, 145, 72, 42, 215, 84, 241, 50, 200, 162, 127, 218, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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