Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c97cb3232ba020542ff640b735ebd30a33e550810228df68a5926bbdd045efa

Tx prefix hash: 531ea17088f534552e64c7c6924afa1dc23b1159374075c56a2e9d39ab8a1792
Tx public key: 60fabd93df5cdacfca041fff1a2b164328f2d7f09d94ddd1b268f97d99d03942
Timestamp: 1712149164 Timestamp [UCT]: 2024-04-03 12:59:24 Age [y:d:h:m:s]: 00:296:10:45:53
Block: 992440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212170 RingCT/type: yes/0
Extra: 0160fabd93df5cdacfca041fff1a2b164328f2d7f09d94ddd1b268f97d99d039420211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58e6c8baf67660b82681007b8fd0a2f8d7ebe6b2819c9e5c2770a8983545e530 0.600000000000 1452782 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": 992450, "vin": [ { "gen": { "height": 992440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58e6c8baf67660b82681007b8fd0a2f8d7ebe6b2819c9e5c2770a8983545e530" } } ], "extra": [ 1, 96, 250, 189, 147, 223, 92, 218, 207, 202, 4, 31, 255, 26, 43, 22, 67, 40, 242, 215, 240, 157, 148, 221, 209, 178, 104, 249, 125, 153, 208, 57, 66, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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