Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1586f15de8127762b21cd054fc211a25895e4cf57279b0b40c67a86915f9f536

Tx prefix hash: 668205eaa248df1de62ade61b418d853688b3a1ae83a98a418e57954c2b580ab
Tx public key: 5ed67551be8e3bbe6f2ac3651915f373ae7610c5bee09cc405a914b76fdfc48f
Timestamp: 1760113873 Timestamp [UCT]: 2025-10-10 16:31:13 Age [y:d:h:m:s]: 00:041:02:51:17
Block: 1387001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29440 RingCT/type: yes/0
Extra: 015ed67551be8e3bbe6f2ac3651915f373ae7610c5bee09cc405a914b76fdfc48f02110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4c1e6542e1bf2c4c59f7ae7b09578704d88b203258f345c1ca4622b21817a78 0.600000000000 1875182 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": 1387011, "vin": [ { "gen": { "height": 1387001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4c1e6542e1bf2c4c59f7ae7b09578704d88b203258f345c1ca4622b21817a78" } } ], "extra": [ 1, 94, 214, 117, 81, 190, 142, 59, 190, 111, 42, 195, 101, 25, 21, 243, 115, 174, 118, 16, 197, 190, 224, 156, 196, 5, 169, 20, 183, 111, 223, 196, 143, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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