Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a1c05d74126cc89b090eb450fa9ea46c2a14d976d567a9a0f9c5afd1329517b

Tx prefix hash: 21daa5b126c72cac7d386afa0b72a6a4437138bcbb3e6d351d338950b98b79d1
Tx public key: 360c0e7a0d4c3fc5c74d27a20b2eb20c788bacf031fcc9523cc4148d574030e4
Timestamp: 1732770107 Timestamp [UCT]: 2024-11-28 05:01:47 Age [y:d:h:m:s]: 00:112:01:28:15
Block: 1163326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79909 RingCT/type: yes/0
Extra: 01360c0e7a0d4c3fc5c74d27a20b2eb20c788bacf031fcc9523cc4148d574030e4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4de150d0c435a72bcb31fa0e9a4123fa194c9ec535332e4de901a0b8e5365540 0.600000000000 1648993 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": 1163336, "vin": [ { "gen": { "height": 1163326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4de150d0c435a72bcb31fa0e9a4123fa194c9ec535332e4de901a0b8e5365540" } } ], "extra": [ 1, 54, 12, 14, 122, 13, 76, 63, 197, 199, 77, 39, 162, 11, 46, 178, 12, 120, 139, 172, 240, 49, 252, 201, 82, 60, 196, 20, 141, 87, 64, 48, 228, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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