Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a6218a7c315eb1c24002bd1160a2f5103b4fed55c8ffae9f6814f8021e1628

Tx prefix hash: 99af7985911b4893dd452055a8a57c01b6ca52ac5d58f802ffc40be87923a75e
Tx public key: f0897c1575ae7e88639518a1b9cca50bc667b3b6afa8aae04fa0a4656c17cef7
Timestamp: 1657471938 Timestamp [UCT]: 2022-07-10 16:52:18 Age [y:d:h:m:s]: 03:114:09:25:27
Block: 540873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 861466 RingCT/type: yes/0
Extra: 01f0897c1575ae7e88639518a1b9cca50bc667b3b6afa8aae04fa0a4656c17cef70211000000074da16a3a000000000000000000

1 output(s) for total of 9.905202751000 dcy

stealth address amount amount idx
00: c14f3e7c1f475e26ad1e62158320a3cb016d021c16c41614c87b0b996f645e0a 9.905202751000 971164 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": 540883, "vin": [ { "gen": { "height": 540873 } } ], "vout": [ { "amount": 9905202751, "target": { "key": "c14f3e7c1f475e26ad1e62158320a3cb016d021c16c41614c87b0b996f645e0a" } } ], "extra": [ 1, 240, 137, 124, 21, 117, 174, 126, 136, 99, 149, 24, 161, 185, 204, 165, 11, 198, 103, 179, 182, 175, 168, 170, 224, 79, 160, 164, 101, 108, 23, 206, 247, 2, 17, 0, 0, 0, 7, 77, 161, 106, 58, 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