Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49b8c6b46b31d4376bf38f8043ac28018a8029359fa11c614bc4bf770f96fed

Tx prefix hash: 8e8a3a117228d5b3d708b1eb329350a330665b9bdec3035a5f0d91e2621374b2
Tx public key: e8e16a75853bdb7b3012e963311c76bd637a548e67a3c15de0e451c732f3358b
Timestamp: 1733837294 Timestamp [UCT]: 2024-12-10 13:28:14 Age [y:d:h:m:s]: 00:036:15:07:03
Block: 1172178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26180 RingCT/type: yes/0
Extra: 01e8e16a75853bdb7b3012e963311c76bd637a548e67a3c15de0e451c732f3358b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f70ab7b5a56cc7da9109b7faf7063cf3e9b7690a04f497defbdac1cac7e7ff8 0.600000000000 1658037 of 15

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": 1172188, "vin": [ { "gen": { "height": 1172178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f70ab7b5a56cc7da9109b7faf7063cf3e9b7690a04f497defbdac1cac7e7ff8" } } ], "extra": [ 1, 232, 225, 106, 117, 133, 59, 219, 123, 48, 18, 233, 99, 49, 28, 118, 189, 99, 122, 84, 142, 103, 163, 193, 93, 224, 228, 81, 199, 50, 243, 53, 139, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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