Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b48ebca603550611cc4591b459d2f2a1f22f544c574144f48154000db2274de

Tx prefix hash: 2a4a11d4f3e6cde6a99b49e4683edcaa830daad5fb7abf2b3217a6a51fffc5d2
Tx public key: 026d82a64ad15583e02e951f75b19b95fe429a16ba191a26aa0af8f71902da11
Timestamp: 1722598508 Timestamp [UCT]: 2024-08-02 11:35:08 Age [y:d:h:m:s]: 00:229:12:02:14
Block: 1079097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163940 RingCT/type: yes/0
Extra: 01026d82a64ad15583e02e951f75b19b95fe429a16ba191a26aa0af8f71902da1102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5deb4000cc061f1fcb02e6af5b467ef7eaeabd4c3824fa9573f1c4b70974316 0.600000000000 1551906 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": 1079107, "vin": [ { "gen": { "height": 1079097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5deb4000cc061f1fcb02e6af5b467ef7eaeabd4c3824fa9573f1c4b70974316" } } ], "extra": [ 1, 2, 109, 130, 166, 74, 209, 85, 131, 224, 46, 149, 31, 117, 177, 155, 149, 254, 66, 154, 22, 186, 25, 26, 38, 170, 10, 248, 247, 25, 2, 218, 17, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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