Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9004c74eea6f6999fe2e7320c8314accc6a63bc1d958e43e934de32ecc2a84e

Tx prefix hash: 6982d3656495f1a3154ad1add820d33e0dc5af38f99a4d45b44bb4ac7e55fed1
Tx public key: f9bf29dca610d2b9e701cbd20420dbe8f4c486110b33b19f739733b6a9a95752
Timestamp: 1718750440 Timestamp [UCT]: 2024-06-18 22:40:40 Age [y:d:h:m:s]: 01:152:10:39:53
Block: 1047196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367518 RingCT/type: yes/0
Extra: 01f9bf29dca610d2b9e701cbd20420dbe8f4c486110b33b19f739733b6a9a957520211000000040bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b56670dd333af468f581e700f30ba72f3b0180d7c208fb48908607c8ae49dc 0.600000000000 1517015 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": 1047206, "vin": [ { "gen": { "height": 1047196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b56670dd333af468f581e700f30ba72f3b0180d7c208fb48908607c8ae49dc" } } ], "extra": [ 1, 249, 191, 41, 220, 166, 16, 210, 185, 231, 1, 203, 210, 4, 32, 219, 232, 244, 196, 134, 17, 11, 51, 177, 159, 115, 151, 51, 182, 169, 169, 87, 82, 2, 17, 0, 0, 0, 4, 11, 186, 22, 215, 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