Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce06a3aeb0acbbd4592c89823f445d08e5ae53583d9023991d9317df8c11509c

Tx prefix hash: 420a4eb61b26dcb0c2d461578b2fc081c723d4407fba8dfe4824d6c660e25154
Tx public key: 1e36bd8495c513504c0544ea4ba000bb681f2779f41743503e5d3edefb194951
Timestamp: 1639407270 Timestamp [UCT]: 2021-12-13 14:54:30 Age [y:d:h:m:s]: 03:017:00:36:24
Block: 394690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791114 RingCT/type: yes/0
Extra: 011e36bd8495c513504c0544ea4ba000bb681f2779f41743503e5d3edefb19495102110000000176899486000000000000000000

1 output(s) for total of 30.215413752000 dcy

stealth address amount amount idx
00: 68218c5906e1a62d8484bd745ad58de1627d6c9162394a032fc233a6f7f0dc05 30.215413752000 792369 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": 394700, "vin": [ { "gen": { "height": 394690 } } ], "vout": [ { "amount": 30215413752, "target": { "key": "68218c5906e1a62d8484bd745ad58de1627d6c9162394a032fc233a6f7f0dc05" } } ], "extra": [ 1, 30, 54, 189, 132, 149, 197, 19, 80, 76, 5, 68, 234, 75, 160, 0, 187, 104, 31, 39, 121, 244, 23, 67, 80, 62, 93, 62, 222, 251, 25, 73, 81, 2, 17, 0, 0, 0, 1, 118, 137, 148, 134, 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