Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: badcb2fdbd188e9b701da1b07af06d01d8a450575b6d31fa0230833aef2a7c1c

Tx prefix hash: 2b10c5d5cb68f26d72a12417cac4b3eeb718576fc7aa6c3c630a0e7ee0c73c89
Tx public key: 15f11de5dc54d2c203fd442675294366c3d2c4e88c896d578075ce54788829a2
Timestamp: 1728882435 Timestamp [UCT]: 2024-10-14 05:07:15 Age [y:d:h:m:s]: 00:089:01:15:28
Block: 1131193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63661 RingCT/type: yes/0
Extra: 0115f11de5dc54d2c203fd442675294366c3d2c4e88c896d578075ce54788829a20211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5c0c1dae4a3755909e5c7cd16f84b063c3568180a0d751eaa3a8e3cf30c049a 0.600000000000 1614074 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": 1131203, "vin": [ { "gen": { "height": 1131193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5c0c1dae4a3755909e5c7cd16f84b063c3568180a0d751eaa3a8e3cf30c049a" } } ], "extra": [ 1, 21, 241, 29, 229, 220, 84, 210, 194, 3, 253, 68, 38, 117, 41, 67, 102, 195, 210, 196, 232, 140, 137, 109, 87, 128, 117, 206, 84, 120, 136, 41, 162, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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