Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1972188b0d4b38c203082c775ab1eeff3b658ffbb3969162701c00b888f79b96

Tx prefix hash: 0cf22e6401f9dc5a090f8cafecf8fecb0c05aa148de8a8168295e7376da16f72
Tx public key: 537271756d08dbd1abd25df1a34fb86bb57e79cd005dc791333a7a163d7dfba8
Timestamp: 1699654679 Timestamp [UCT]: 2023-11-10 22:17:59 Age [y:d:h:m:s]: 01:150:12:57:19
Block: 888886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368783 RingCT/type: yes/0
Extra: 01537271756d08dbd1abd25df1a34fb86bb57e79cd005dc791333a7a163d7dfba8021100000006faf35c9c000000000000000000

1 output(s) for total of 0.696228324000 dcy

stealth address amount amount idx
00: f866649c8ecf07fb082a5e425fb0be28b45b4024a6cbaf44970934b7d70aa832 0.696228324000 1344853 of 0

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": 888896, "vin": [ { "gen": { "height": 888886 } } ], "vout": [ { "amount": 696228324, "target": { "key": "f866649c8ecf07fb082a5e425fb0be28b45b4024a6cbaf44970934b7d70aa832" } } ], "extra": [ 1, 83, 114, 113, 117, 109, 8, 219, 209, 171, 210, 93, 241, 163, 79, 184, 107, 181, 126, 121, 205, 0, 93, 199, 145, 51, 58, 122, 22, 61, 125, 251, 168, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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