Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e111752f1ab57f41bbc510b4f6e807d49101ec5bf7a2b3f9a2761e22e94305de

Tx prefix hash: a1e7d8ac741fd1ecca42ca9887701d743a010b9c2467f78187508625cd68dcef
Tx public key: d4e2e4148e0b5e552dd8659f7efb2ea113985deee5f1d7a38d32b032d84418d3
Timestamp: 1726491682 Timestamp [UCT]: 2024-09-16 13:01:22 Age [y:d:h:m:s]: 00:115:18:48:15
Block: 1111383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82783 RingCT/type: yes/0
Extra: 01d4e2e4148e0b5e552dd8659f7efb2ea113985deee5f1d7a38d32b032d84418d3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dfda351e753c2fab55d0a8e0fef64296e38df7dcae3d9e4a78e66ec7672346d 0.600000000000 1590318 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": 1111393, "vin": [ { "gen": { "height": 1111383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dfda351e753c2fab55d0a8e0fef64296e38df7dcae3d9e4a78e66ec7672346d" } } ], "extra": [ 1, 212, 226, 228, 20, 142, 11, 94, 85, 45, 216, 101, 159, 126, 251, 46, 161, 19, 152, 93, 238, 229, 241, 215, 163, 141, 50, 176, 50, 216, 68, 24, 211, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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