Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9b889e164a60227bf8191d29a6685475583d1d55532f0250f5c475ca3de41c

Tx prefix hash: 81160af383d589a8c6f15181cdd1ea846fe6fea7ba5bcf74617c173eb00dbdf7
Tx public key: c914938c6e2b269cf7d8e8d293c4863e84433333dc28dcefea9019f10ba1af14
Timestamp: 1705458868 Timestamp [UCT]: 2024-01-17 02:34:28 Age [y:d:h:m:s]: 01:006:21:27:15
Block: 936972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266225 RingCT/type: yes/0
Extra: 01c914938c6e2b269cf7d8e8d293c4863e84433333dc28dcefea9019f10ba1af1402110000001e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac153b5de6adaa2d6ade753d0ccbb85494e9dedc63ae76e415305dcfdc72903e 0.600000000000 1395016 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": 936982, "vin": [ { "gen": { "height": 936972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac153b5de6adaa2d6ade753d0ccbb85494e9dedc63ae76e415305dcfdc72903e" } } ], "extra": [ 1, 201, 20, 147, 140, 110, 43, 38, 156, 247, 216, 232, 210, 147, 196, 134, 62, 132, 67, 51, 51, 220, 40, 220, 239, 234, 144, 25, 241, 11, 161, 175, 20, 2, 17, 0, 0, 0, 30, 89, 218, 211, 245, 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