Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747cc3198f8be2848e1258175a4674a787e96d2a53671b715e8219710cd73caf

Tx prefix hash: e500c09d6626abe4f51388362f6c278a1d87627bb3f732b64f98468a08c2f145
Tx public key: 081a0345ea742a1178fd07dd84b648dd4aaee91443928a83dc480737c2ef6a0f
Timestamp: 1594000640 Timestamp [UCT]: 2020-07-06 01:57:20 Age [y:d:h:m:s]: 04:215:12:07:42
Block: 114285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098400 RingCT/type: yes/0
Extra: 01081a0345ea742a1178fd07dd84b648dd4aaee91443928a83dc480737c2ef6a0f02110000000f4b611f06000000000000000000

1 output(s) for total of 256.641624013000 dcy

stealth address amount amount idx
00: 4ce4de5d74349a250bcea982a17a5907e0ab28c0a3cfed35f244e9e687d3596c 256.641624013000 196335 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": 114295, "vin": [ { "gen": { "height": 114285 } } ], "vout": [ { "amount": 256641624013, "target": { "key": "4ce4de5d74349a250bcea982a17a5907e0ab28c0a3cfed35f244e9e687d3596c" } } ], "extra": [ 1, 8, 26, 3, 69, 234, 116, 42, 17, 120, 253, 7, 221, 132, 182, 72, 221, 74, 174, 233, 20, 67, 146, 138, 131, 220, 72, 7, 55, 194, 239, 106, 15, 2, 17, 0, 0, 0, 15, 75, 97, 31, 6, 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