Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1947b331382081e341b67c7ee9acf502c9be322e8f344b0005d52b2e3ef96a21

Tx prefix hash: 977b9a3759f1f6fb1d171f5d277120f53fdaf1f7f57f40c6b277004d3b5760a7
Tx public key: 8fd0f56b474bb5a92f91f9fdb354843e38fbe57bb0154ec861fac13e9c17ddf7
Timestamp: 1608499823 Timestamp [UCT]: 2020-12-20 21:30:23 Age [y:d:h:m:s]: 04:069:12:31:53
Block: 166034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1062259 RingCT/type: yes/0
Extra: 018fd0f56b474bb5a92f91f9fdb354843e38fbe57bb0154ec861fac13e9c17ddf70211000002804ea414e5000000000000000000

1 output(s) for total of 172.934202444000 dcy

stealth address amount amount idx
00: a9653e56b50fca0f4b0428f193d5ba25b42ee3e189ba7955d8d6447f793f7bb3 172.934202444000 303239 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": 166044, "vin": [ { "gen": { "height": 166034 } } ], "vout": [ { "amount": 172934202444, "target": { "key": "a9653e56b50fca0f4b0428f193d5ba25b42ee3e189ba7955d8d6447f793f7bb3" } } ], "extra": [ 1, 143, 208, 245, 107, 71, 75, 181, 169, 47, 145, 249, 253, 179, 84, 132, 62, 56, 251, 229, 123, 176, 21, 78, 200, 97, 250, 193, 62, 156, 23, 221, 247, 2, 17, 0, 0, 2, 128, 78, 164, 20, 229, 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