Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28a7c2fd8120436f30f7a79aa68ee50ffe4c0ec9a7f92ab6af41bf0cdd57c11

Tx prefix hash: 837512122fd91d162ec87fd4217751a09bf652753a19ebfd9e5085b6454d681b
Tx public key: 1bf3d265a77075ebd6a17f5f0faed7b8227de6e666b16b039db50be2af1186b6
Timestamp: 1727177090 Timestamp [UCT]: 2024-09-24 11:24:50 Age [y:d:h:m:s]: 00:151:17:34:03
Block: 1117059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108210 RingCT/type: yes/0
Extra: 011bf3d265a77075ebd6a17f5f0faed7b8227de6e666b16b039db50be2af1186b6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40a4f8693da85e552895a4633e4779abc3e502111bb36a08b18c4d866a2d210e 0.600000000000 1597758 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": 1117069, "vin": [ { "gen": { "height": 1117059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40a4f8693da85e552895a4633e4779abc3e502111bb36a08b18c4d866a2d210e" } } ], "extra": [ 1, 27, 243, 210, 101, 167, 112, 117, 235, 214, 161, 127, 95, 15, 174, 215, 184, 34, 125, 230, 230, 102, 177, 107, 3, 157, 181, 11, 226, 175, 17, 134, 182, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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