Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b987e0928045739bab3c49deaa00d0e29f56f13de5de2640369f2e86ca78745a

Tx prefix hash: 709d186f72ad3f80098bccd247e0ce7aa1bed1b6576dc0321b4eaf9631a8fe10
Tx public key: aa083311fd95305a943916d1f2fce1155286254a2cd082b2402b2423a2c4c2c4
Timestamp: 1641080831 Timestamp [UCT]: 2022-01-01 23:47:11 Age [y:d:h:m:s]: 03:120:03:25:17
Block: 408496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864649 RingCT/type: yes/0
Extra: 01aa083311fd95305a943916d1f2fce1155286254a2cd082b2402b2423a2c4c2c402110000003d58821d9c000000000000000000

1 output(s) for total of 27.194652660000 dcy

stealth address amount amount idx
00: 1d0039992a1a857d12515ad46438e4f7dfd792bb1ab2a0b0108ab337ee90dd18 27.194652660000 810565 of 0

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": 408506, "vin": [ { "gen": { "height": 408496 } } ], "vout": [ { "amount": 27194652660, "target": { "key": "1d0039992a1a857d12515ad46438e4f7dfd792bb1ab2a0b0108ab337ee90dd18" } } ], "extra": [ 1, 170, 8, 51, 17, 253, 149, 48, 90, 148, 57, 22, 209, 242, 252, 225, 21, 82, 134, 37, 74, 44, 208, 130, 178, 64, 43, 36, 35, 162, 196, 194, 196, 2, 17, 0, 0, 0, 61, 88, 130, 29, 156, 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