Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51228c0f16d678734078ae2af4ad04e0e48fa486c0469698f69f8b7fd410eb16

Tx prefix hash: 002800b1ebcec4c1a7290f28f08c6ae505b6d8ead66ca827d0e3b27ee2d47a85
Tx public key: a44cc028b15dd91d76146ad1233273b84f9623157b24bc9803b99c23930913d5
Timestamp: 1734605541 Timestamp [UCT]: 2024-12-19 10:52:21 Age [y:d:h:m:s]: 00:108:17:44:36
Block: 1178549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77473 RingCT/type: yes/0
Extra: 01a44cc028b15dd91d76146ad1233273b84f9623157b24bc9803b99c23930913d50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88fa3cc0859f7fa5ecf56da26d70b5f0a2e0a9c6bbb39ece0a4661d224a89af0 0.600000000000 1664936 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": 1178559, "vin": [ { "gen": { "height": 1178549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88fa3cc0859f7fa5ecf56da26d70b5f0a2e0a9c6bbb39ece0a4661d224a89af0" } } ], "extra": [ 1, 164, 76, 192, 40, 177, 93, 217, 29, 118, 20, 106, 209, 35, 50, 115, 184, 79, 150, 35, 21, 123, 36, 188, 152, 3, 185, 156, 35, 147, 9, 19, 213, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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