Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4c43f701457cd53fb7bfd6fb864197a8457c6ba1008e4b2ce4ae74f632cff0

Tx prefix hash: d6e42d37b40813227997a3e19963763f850b618ec81be951c4e4eec025931897
Tx public key: 8fdbdaa8adf0d726d1912977d991ca26e92efc5a617bc0e2370a7870b2bb3265
Timestamp: 1710450668 Timestamp [UCT]: 2024-03-14 21:11:08 Age [y:d:h:m:s]: 01:239:15:25:45
Block: 978407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429962 RingCT/type: yes/0
Extra: 018fdbdaa8adf0d726d1912977d991ca26e92efc5a617bc0e2370a7870b2bb326502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a40c946ef327cfb2d02ffd4fe2866079abd7d45b049080bdfc89f5c797b232 0.600000000000 1438434 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": 978417, "vin": [ { "gen": { "height": 978407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a40c946ef327cfb2d02ffd4fe2866079abd7d45b049080bdfc89f5c797b232" } } ], "extra": [ 1, 143, 219, 218, 168, 173, 240, 215, 38, 209, 145, 41, 119, 217, 145, 202, 38, 233, 46, 252, 90, 97, 123, 192, 226, 55, 10, 120, 112, 178, 187, 50, 101, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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