Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f124a9da78949abd43e2b154ba73b2f6f61ae6d67db3246fd774217af70d5bab

Tx prefix hash: bb2abda0a40e0cc8ed777a86fbe18ec33ec6e0e0b32a59dca6f3ee7143ac139e
Tx public key: 48433b04529a1a9c67727769138094dfc3c0a4817d8cff884492219c31323d4b
Timestamp: 1716791849 Timestamp [UCT]: 2024-05-27 06:37:29 Age [y:d:h:m:s]: 00:338:14:08:25
Block: 1030969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241991 RingCT/type: yes/0
Extra: 0148433b04529a1a9c67727769138094dfc3c0a4817d8cff884492219c31323d4b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ba75b05a3f4b2c64ba7b9585baa15c91902f3e7c5c3eed27a655618f282ce9d 0.600000000000 1499300 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": 1030979, "vin": [ { "gen": { "height": 1030969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba75b05a3f4b2c64ba7b9585baa15c91902f3e7c5c3eed27a655618f282ce9d" } } ], "extra": [ 1, 72, 67, 59, 4, 82, 154, 26, 156, 103, 114, 119, 105, 19, 128, 148, 223, 195, 192, 164, 129, 125, 140, 255, 136, 68, 146, 33, 156, 49, 50, 61, 75, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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