Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e10ecd4b5fb92f6c824dee48de529103e49ff09cfd106de5f657a0c77b0992

Tx prefix hash: df6658b26f8ceac404ee0013074f5f3de6ca38dfde65e99a889f8b0b4dff38e7
Tx public key: 6a3435f2251418b907fb0ed2c4bdd1638aa9a94da7ccfe78d579561f8935c00a
Timestamp: 1743328833 Timestamp [UCT]: 2025-03-30 10:00:33 Age [y:d:h:m:s]: 00:276:19:15:50
Block: 1250473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195624 RingCT/type: yes/0
Extra: 016a3435f2251418b907fb0ed2c4bdd1638aa9a94da7ccfe78d579561f8935c00a0211000000111a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0b1da85f447d9c27644956b202a272e49b0528ad46815b0f6439be7677f6ce5 0.600000000000 1737522 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": 1250483, "vin": [ { "gen": { "height": 1250473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0b1da85f447d9c27644956b202a272e49b0528ad46815b0f6439be7677f6ce5" } } ], "extra": [ 1, 106, 52, 53, 242, 37, 20, 24, 185, 7, 251, 14, 210, 196, 189, 209, 99, 138, 169, 169, 77, 167, 204, 254, 120, 213, 121, 86, 31, 137, 53, 192, 10, 2, 17, 0, 0, 0, 17, 26, 151, 4, 3, 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