Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ff809864e65ae56f60b277339568accd4ebdf6e25c0a402643659de8198034

Tx prefix hash: 1397cb8bbc45ca18ca0ed36c4410e3fa3d2fcee5be8e3c7811c75319c0fb5be5
Tx public key: cf1a8a5dec5a58f803f70834b0b2e00836bfd1d30a0f1c7d5662c8a34efb6dc2
Timestamp: 1697217763 Timestamp [UCT]: 2023-10-13 17:22:43 Age [y:d:h:m:s]: 01:248:19:14:04
Block: 868884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438774 RingCT/type: yes/0
Extra: 01cf1a8a5dec5a58f803f70834b0b2e00836bfd1d30a0f1c7d5662c8a34efb6dc2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.811010816000 dcy

stealth address amount amount idx
00: 089ba6c961261cb549edf0adeed43cbc465bc091a472777a456b8d4b55a1cadf 0.811010816000 1323709 of 0

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": 868894, "vin": [ { "gen": { "height": 868884 } } ], "vout": [ { "amount": 811010816, "target": { "key": "089ba6c961261cb549edf0adeed43cbc465bc091a472777a456b8d4b55a1cadf" } } ], "extra": [ 1, 207, 26, 138, 93, 236, 90, 88, 248, 3, 247, 8, 52, 176, 178, 224, 8, 54, 191, 209, 211, 10, 15, 28, 125, 86, 98, 200, 163, 78, 251, 109, 194, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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