Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bb75ed69d8cb5ed51eb47751cff7c12e3adad4b762fd304f310b4a44854a23b

Tx prefix hash: 42651cb512d4a05fcf4475157658a2b83c68b0c65956267dab9801950e7d6070
Tx public key: b202a5bc7332b5d57bea3c8a083b5d41f8fba01bde01741047b4af3ee1834404
Timestamp: 1712375543 Timestamp [UCT]: 2024-04-06 03:52:23 Age [y:d:h:m:s]: 01:038:21:35:20
Block: 994310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288814 RingCT/type: yes/0
Extra: 01b202a5bc7332b5d57bea3c8a083b5d41f8fba01bde01741047b4af3ee18344040211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cdc9c4d47f0f31f859f7bb4ed9bff8600f445e5a10f02a213fcbf5584efed7b 0.600000000000 1454712 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": 994320, "vin": [ { "gen": { "height": 994310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cdc9c4d47f0f31f859f7bb4ed9bff8600f445e5a10f02a213fcbf5584efed7b" } } ], "extra": [ 1, 178, 2, 165, 188, 115, 50, 181, 213, 123, 234, 60, 138, 8, 59, 93, 65, 248, 251, 160, 27, 222, 1, 116, 16, 71, 180, 175, 62, 225, 131, 68, 4, 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