Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12db8f88edb242cac785b6c56bb03d3917b79a4cf814eb7b1ce69adae9485f86

Tx prefix hash: cee71ad893cb9a8b670c04638e1b7cf60c619e46b2a5cc42b0b89338de0b3065
Tx public key: b44a85dd315b4d288ff9512ce968e4a121354f737a5dfad6c438fe936f7f0117
Timestamp: 1729513977 Timestamp [UCT]: 2024-10-21 12:32:57 Age [y:d:h:m:s]: 00:192:17:12:15
Block: 1136397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137550 RingCT/type: yes/0
Extra: 01b44a85dd315b4d288ff9512ce968e4a121354f737a5dfad6c438fe936f7f0117021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f00572bc0ce59c0dface11de4412f9ea36b47a796e6b592c5ff85382e72956cb 0.600000000000 1619742 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": 1136407, "vin": [ { "gen": { "height": 1136397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f00572bc0ce59c0dface11de4412f9ea36b47a796e6b592c5ff85382e72956cb" } } ], "extra": [ 1, 180, 74, 133, 221, 49, 91, 77, 40, 143, 249, 81, 44, 233, 104, 228, 161, 33, 53, 79, 115, 122, 93, 250, 214, 196, 56, 254, 147, 111, 127, 1, 23, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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