Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 474dfea60f452d72093d3d2859cc54135763c7c2f7eb141c7ee3a27273b23432

Tx prefix hash: be14b008e9ee9fafb567bdbf94c2ef029f9ba8bf4ddae8a50d299133865e2485
Tx public key: e1d1b7b0567e0bade33cfc61d6d50c088c5d3a24c2763101c33195f6011538f5
Timestamp: 1762271213 Timestamp [UCT]: 2025-11-04 15:46:53 Age [y:d:h:m:s]: 00:006:05:47:29
Block: 1404884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4467 RingCT/type: yes/0
Extra: 01e1d1b7b0567e0bade33cfc61d6d50c088c5d3a24c2763101c33195f6011538f50211000000085dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7940cb3abb8f1fdf0d96b91b519aefbb8167b9943a2870a742dabbb104581f54 0.600000000000 1893251 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": 1404894, "vin": [ { "gen": { "height": 1404884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7940cb3abb8f1fdf0d96b91b519aefbb8167b9943a2870a742dabbb104581f54" } } ], "extra": [ 1, 225, 209, 183, 176, 86, 126, 11, 173, 227, 60, 252, 97, 214, 213, 12, 8, 140, 93, 58, 36, 194, 118, 49, 1, 195, 49, 149, 246, 1, 21, 56, 245, 2, 17, 0, 0, 0, 8, 93, 251, 190, 42, 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