Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8a6c1de54a61c77604d1210f5a0a4c5a8b985ec9a3c4f9a82aac64646d099e8

Tx prefix hash: 1086ca766f69cdb2d13466eb3f3109b5b5a9b78d4945046df0aae906d9d775c7
Tx public key: 0bc879980f5dc4d71056284e5f817393f83a44ff79b85d06bfb921badc1756e0
Timestamp: 1730061978 Timestamp [UCT]: 2024-10-27 20:46:18 Age [y:d:h:m:s]: 00:085:17:21:19
Block: 1140935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61247 RingCT/type: yes/0
Extra: 010bc879980f5dc4d71056284e5f817393f83a44ff79b85d06bfb921badc1756e0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45cf31283642d74f616c233bed648790139ad9040c43e12e916e9865f2834c68 0.600000000000 1624740 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": 1140945, "vin": [ { "gen": { "height": 1140935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45cf31283642d74f616c233bed648790139ad9040c43e12e916e9865f2834c68" } } ], "extra": [ 1, 11, 200, 121, 152, 15, 93, 196, 215, 16, 86, 40, 78, 95, 129, 115, 147, 248, 58, 68, 255, 121, 184, 93, 6, 191, 185, 33, 186, 220, 23, 86, 224, 2, 17, 0, 0, 0, 4, 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