Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 881a03f17502da17c767fd6d973ef6fc364d4619e9135f066c02b79a52839b7a

Tx prefix hash: 8110d36beb2ad4e60356d48cb5f87276482b7191bcc8352bc30c687d82ffdaf8
Tx public key: a9c7b1d239e2660756e43895881a8383dbb3d726dcbfdcb8c250abfed0aa71f5
Timestamp: 1617543725 Timestamp [UCT]: 2021-04-04 13:42:05 Age [y:d:h:m:s]: 04:211:02:49:40
Block: 233103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168948 RingCT/type: yes/0
Extra: 01a9c7b1d239e2660756e43895881a8383dbb3d726dcbfdcb8c250abfed0aa71f50211000000113634f08d000000000000000000

1 output(s) for total of 103.665339040000 dcy

stealth address amount amount idx
00: 0eeea4649d7b9d5f8f087981902f6c0d8ab3b5b8523e84bd4b9f897d8d7d98a9 103.665339040000 484165 of 0

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": 233113, "vin": [ { "gen": { "height": 233103 } } ], "vout": [ { "amount": 103665339040, "target": { "key": "0eeea4649d7b9d5f8f087981902f6c0d8ab3b5b8523e84bd4b9f897d8d7d98a9" } } ], "extra": [ 1, 169, 199, 177, 210, 57, 226, 102, 7, 86, 228, 56, 149, 136, 26, 131, 131, 219, 179, 215, 38, 220, 191, 220, 184, 194, 80, 171, 254, 208, 170, 113, 245, 2, 17, 0, 0, 0, 17, 54, 52, 240, 141, 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