Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a244479208a968b2e83cfc2685d6bac40e0aca91fbffb07382d4240de7b9912c

Tx prefix hash: 1a2a8935ec46f852c2024f627fff7e76cf6e23ca66ded8a572e6df57cfb181f7
Tx public key: 77bd19f059af7ad9e6651e5d202264e24fcc4dba77e8f749ff483e611cd2e67c
Timestamp: 1637528491 Timestamp [UCT]: 2021-11-21 21:01:31 Age [y:d:h:m:s]: 03:158:03:07:01
Block: 379208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 891723 RingCT/type: yes/0
Extra: 0177bd19f059af7ad9e6651e5d202264e24fcc4dba77e8f749ff483e611cd2e67c02110000000e1cab2639000000000000000000

1 output(s) for total of 34.004343651000 dcy

stealth address amount amount idx
00: a8d0afe2ddb63b11ae5f935c77970809b1eb0206dac5b4bae58925bc9153a6ee 34.004343651000 766608 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": 379218, "vin": [ { "gen": { "height": 379208 } } ], "vout": [ { "amount": 34004343651, "target": { "key": "a8d0afe2ddb63b11ae5f935c77970809b1eb0206dac5b4bae58925bc9153a6ee" } } ], "extra": [ 1, 119, 189, 25, 240, 89, 175, 122, 217, 230, 101, 30, 93, 32, 34, 100, 226, 79, 204, 77, 186, 119, 232, 247, 73, 255, 72, 62, 97, 28, 210, 230, 124, 2, 17, 0, 0, 0, 14, 28, 171, 38, 57, 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