Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f228abd166e01062231b4e38f665f77d5a5cde62b11b8adc525cc47dbdb2ef

Tx prefix hash: b50cf7a10488ca161f837c1c6b68331f710d57f0352c4716508b05f35ce7e150
Tx public key: 721d69fed2b58c6dde74c6b6e9da74e0cc89a8dfc446bc9953e8f897d12bc814
Timestamp: 1626548206 Timestamp [UCT]: 2021-07-17 18:56:46 Age [y:d:h:m:s]: 03:136:06:36:32
Block: 295821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 868837 RingCT/type: yes/0
Extra: 01721d69fed2b58c6dde74c6b6e9da74e0cc89a8dfc446bc9953e8f897d12bc8140211000000183525d189000000000000000000

1 output(s) for total of 64.242542792000 dcy

stealth address amount amount idx
00: 5f41f57aa9e3004f395f323335c134cadd995e88d3f25e26ccbacfea6d6b65ac 64.242542792000 619417 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": 295831, "vin": [ { "gen": { "height": 295821 } } ], "vout": [ { "amount": 64242542792, "target": { "key": "5f41f57aa9e3004f395f323335c134cadd995e88d3f25e26ccbacfea6d6b65ac" } } ], "extra": [ 1, 114, 29, 105, 254, 210, 181, 140, 109, 222, 116, 198, 182, 233, 218, 116, 224, 204, 137, 168, 223, 196, 70, 188, 153, 83, 232, 248, 151, 209, 43, 200, 20, 2, 17, 0, 0, 0, 24, 53, 37, 209, 137, 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