Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4548aefddadb4bb88fbdb3c0070e26da1b2e9dc6233d51f0306f0f50e1cade9b

Tx prefix hash: 413c1d886e5ee63c3d57d13b1f3796d20388cde166d38f67bd3e684ac836cfc8
Tx public key: d3eb695fd74be5f8445c9c6b537b0ede9270a4b589e816fed077aa24e742b9ff
Timestamp: 1715787474 Timestamp [UCT]: 2024-05-15 15:37:54 Age [y:d:h:m:s]: 00:336:11:52:38
Block: 1022633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240519 RingCT/type: yes/0
Extra: 01d3eb695fd74be5f8445c9c6b537b0ede9270a4b589e816fed077aa24e742b9ff0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 966fb47b48ea5fddbaae3d46dd41dda386a47ca88a470dd3078ed46c71732f01 0.600000000000 1487294 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": 1022643, "vin": [ { "gen": { "height": 1022633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "966fb47b48ea5fddbaae3d46dd41dda386a47ca88a470dd3078ed46c71732f01" } } ], "extra": [ 1, 211, 235, 105, 95, 215, 75, 229, 248, 68, 92, 156, 107, 83, 123, 14, 222, 146, 112, 164, 181, 137, 232, 22, 254, 208, 119, 170, 36, 231, 66, 185, 255, 2, 17, 0, 0, 0, 1, 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