Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e36139c7b30f6d6a4a9aba7fcd551f990f30321c90530e2f7149814a8c70f1

Tx prefix hash: 3f6024154b3b6d50edc24e4bd523019eea2ffcb5d7186ef534fffa34faf704f5
Tx public key: a1570bbb35082c1b3bd84a9143aa4704889bda87dbfccdc334d05371396e5f87
Timestamp: 1711367066 Timestamp [UCT]: 2024-03-25 11:44:26 Age [y:d:h:m:s]: 01:043:17:41:45
Block: 986009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292216 RingCT/type: yes/0
Extra: 01a1570bbb35082c1b3bd84a9143aa4704889bda87dbfccdc334d05371396e5f870211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b72c81e8394bc0399076f2c0d01410860229c19ed8d74a78f53de36e66e0ebd 0.600000000000 1446234 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": 986019, "vin": [ { "gen": { "height": 986009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b72c81e8394bc0399076f2c0d01410860229c19ed8d74a78f53de36e66e0ebd" } } ], "extra": [ 1, 161, 87, 11, 187, 53, 8, 44, 27, 59, 216, 74, 145, 67, 170, 71, 4, 136, 155, 218, 135, 219, 252, 205, 195, 52, 208, 83, 113, 57, 110, 95, 135, 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