Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d88b11939553df4d65dfc7421327384fe03c48ff1861093434a63d1c15e7b1

Tx prefix hash: 334873ce226a000e99088231b71a61f866300c5216daf8fda3ef5d241d3dedf8
Tx public key: a901b2ac639296baf80abf4a3c4de383a3e1747ea0f9c8c5628d6eceb14923b4
Timestamp: 1716706010 Timestamp [UCT]: 2024-05-26 06:46:50 Age [y:d:h:m:s]: 00:294:20:12:01
Block: 1030256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210719 RingCT/type: yes/0
Extra: 01a901b2ac639296baf80abf4a3c4de383a3e1747ea0f9c8c5628d6eceb14923b402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcec6aae70ac7c53a3361093267beb96c162ce2beeba6ce28eb7a94979ef76aa 0.600000000000 1498511 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": 1030266, "vin": [ { "gen": { "height": 1030256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcec6aae70ac7c53a3361093267beb96c162ce2beeba6ce28eb7a94979ef76aa" } } ], "extra": [ 1, 169, 1, 178, 172, 99, 146, 150, 186, 248, 10, 191, 74, 60, 77, 227, 131, 163, 225, 116, 126, 160, 249, 200, 197, 98, 141, 110, 206, 177, 73, 35, 180, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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