Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13dbb3b4737c21355c50d4fec886313766738de3d8b3a3776f7991c09a3a7272

Tx prefix hash: 329caa433150dbb231c376476809e8c995f19a4795cecba37118ef036ce18b05
Tx public key: f6821efbd73eaa7e1bffef04213d711e20b96893f5bff4b03a8117888b1b080b
Timestamp: 1739119234 Timestamp [UCT]: 2025-02-09 16:40:34 Age [y:d:h:m:s]: 00:357:21:32:19
Block: 1215635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253470 RingCT/type: yes/0
Extra: 01f6821efbd73eaa7e1bffef04213d711e20b96893f5bff4b03a8117888b1b080b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2c0f91d4c2182ec93f44fe23955c790c5039e1d7fd65549dd2fc85b8f153541 0.600000000000 1702434 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": 1215645, "vin": [ { "gen": { "height": 1215635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2c0f91d4c2182ec93f44fe23955c790c5039e1d7fd65549dd2fc85b8f153541" } } ], "extra": [ 1, 246, 130, 30, 251, 215, 62, 170, 126, 27, 255, 239, 4, 33, 61, 113, 30, 32, 185, 104, 147, 245, 191, 244, 176, 58, 129, 23, 136, 139, 27, 8, 11, 2, 17, 0, 0, 0, 3, 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