Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b97d5c8f75f9c8016e92d5996afeeecab1e72ff8fdebea427d8eb368b6e2d19b

Tx prefix hash: 83045ad25e785a2c3aae14886c3853be9de8fb35e37dab880fca2977b34edd07
Tx public key: 0803613080c64a24f8f4f9aa909fb81bad0711175b9ddccfdb3d81b6cd357c88
Timestamp: 1700891690 Timestamp [UCT]: 2023-11-25 05:54:50 Age [y:d:h:m:s]: 01:096:17:19:29
Block: 899134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330264 RingCT/type: yes/0
Extra: 010803613080c64a24f8f4f9aa909fb81bad0711175b9ddccfdb3d81b6cd357c88021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.643866448000 dcy

stealth address amount amount idx
00: b06ed72f750ebc66203b67a84260a66420f20aed496cf2f95a3cbcfaae616506 0.643866448000 1355577 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": 899144, "vin": [ { "gen": { "height": 899134 } } ], "vout": [ { "amount": 643866448, "target": { "key": "b06ed72f750ebc66203b67a84260a66420f20aed496cf2f95a3cbcfaae616506" } } ], "extra": [ 1, 8, 3, 97, 48, 128, 198, 74, 36, 248, 244, 249, 170, 144, 159, 184, 27, 173, 7, 17, 23, 91, 157, 220, 207, 219, 61, 129, 182, 205, 53, 124, 136, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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