Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4b105a6fb1666d931152da9b8980491dde4f5bc0864fe3d32a5e7c8be7e4549

Tx prefix hash: eb286f4b6a52e9b7ffbcf81a0324638ec23c996974e052e109ae2396045af96a
Tx public key: 31aba460a138291d9084e399c0fd0d138dcf0844387ac39a8934e0fda67c145e
Timestamp: 1709611529 Timestamp [UCT]: 2024-03-05 04:05:29 Age [y:d:h:m:s]: 01:217:17:08:43
Block: 971435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414266 RingCT/type: yes/0
Extra: 0131aba460a138291d9084e399c0fd0d138dcf0844387ac39a8934e0fda67c145e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844d751950f9769d7e1c55df6e4178aae15b77e32e36a3755d842a547c593c0a 0.600000000000 1431330 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": 971445, "vin": [ { "gen": { "height": 971435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844d751950f9769d7e1c55df6e4178aae15b77e32e36a3755d842a547c593c0a" } } ], "extra": [ 1, 49, 171, 164, 96, 161, 56, 41, 29, 144, 132, 227, 153, 192, 253, 13, 19, 141, 207, 8, 68, 56, 122, 195, 154, 137, 52, 224, 253, 166, 124, 20, 94, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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