Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3e400b8ab3c8e7cfbf877a8c5148d51a837b05a74f08c0e807a3c836c8b4f29

Tx prefix hash: ebcf5dfa670e6f76b621315c6779c29162b7ec77c4b303d2a1bf142cf68f7e6b
Tx public key: 457889a3198c1ad20f3ee83dfa3471e9bcab98b63bad04086827bb98e4dfa901
Timestamp: 1704311075 Timestamp [UCT]: 2024-01-03 19:44:35 Age [y:d:h:m:s]: 01:092:17:18:53
Block: 927493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327363 RingCT/type: yes/0
Extra: 01457889a3198c1ad20f3ee83dfa3471e9bcab98b63bad04086827bb98e4dfa901021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 879042912730d8c6e2cce9a05f12232436719a1b87b42222f27b2f7bac8984a0 0.600000000000 1385329 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": 927503, "vin": [ { "gen": { "height": 927493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879042912730d8c6e2cce9a05f12232436719a1b87b42222f27b2f7bac8984a0" } } ], "extra": [ 1, 69, 120, 137, 163, 25, 140, 26, 210, 15, 62, 232, 61, 250, 52, 113, 233, 188, 171, 152, 182, 59, 173, 4, 8, 104, 39, 187, 152, 228, 223, 169, 1, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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