Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec1ab84bf8e56b5a7e46fec70fbf21605c34e2a3b476f2e91a29e0033d4ecf88

Tx prefix hash: f59d791f028dee74faf05b599c09b78d4aff5de50ad60c90bb7533ee3dc01b8b
Tx public key: ff0cb4ea808c137c419edae71989afe6dc2f0130ee197b75f90876d7b6444edf
Timestamp: 1731942112 Timestamp [UCT]: 2024-11-18 15:01:52 Age [y:d:h:m:s]: 00:137:07:13:54
Block: 1156455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97962 RingCT/type: yes/0
Extra: 01ff0cb4ea808c137c419edae71989afe6dc2f0130ee197b75f90876d7b6444edf021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a4a452dc32f46d746889fd0a519afe200a44161010e6a77262cacf09124400 0.600000000000 1642078 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": 1156465, "vin": [ { "gen": { "height": 1156455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a4a452dc32f46d746889fd0a519afe200a44161010e6a77262cacf09124400" } } ], "extra": [ 1, 255, 12, 180, 234, 128, 140, 19, 124, 65, 158, 218, 231, 25, 137, 175, 230, 220, 47, 1, 48, 238, 25, 123, 117, 249, 8, 118, 215, 182, 68, 78, 223, 2, 17, 0, 0, 0, 1, 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