Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db5b4635b23672461c70ab86b4b077cf7c266d3f415eeb41e9843213b476218b

Tx prefix hash: ac1fdb6c4ddbf0883d9d5718eed7f39935adabfa1a6156c552af22a31e4777a4
Tx public key: a144b800f9622b16b144a61b9acc02a8a0e43e872bdb83320c61f6af59c5ca3d
Timestamp: 1727103210 Timestamp [UCT]: 2024-09-23 14:53:30 Age [y:d:h:m:s]: 00:205:13:59:34
Block: 1116440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146757 RingCT/type: yes/0
Extra: 01a144b800f9622b16b144a61b9acc02a8a0e43e872bdb83320c61f6af59c5ca3d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc48a9acf41ca779110d9582dd325dbd763418ccba04aa814fa1e9cb5bbdcd1 0.600000000000 1596923 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": 1116450, "vin": [ { "gen": { "height": 1116440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc48a9acf41ca779110d9582dd325dbd763418ccba04aa814fa1e9cb5bbdcd1" } } ], "extra": [ 1, 161, 68, 184, 0, 249, 98, 43, 22, 177, 68, 166, 27, 154, 204, 2, 168, 160, 228, 62, 135, 43, 219, 131, 50, 12, 97, 246, 175, 89, 197, 202, 61, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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