Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31cd460fea505fc431e3e875a5f20f3f8e266066b99da5ee6a4d89fcb1cead85

Tx prefix hash: b383de11985c38562a76227068af9ef27915b3361283bc31d342d8be937ad6e0
Tx public key: 826b0f39bd27c1f3f5915cd5d33d75b7445b169de66a84228553dc209d90c5a2
Timestamp: 1702343127 Timestamp [UCT]: 2023-12-12 01:05:27 Age [y:d:h:m:s]: 01:039:16:05:36
Block: 911175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289675 RingCT/type: yes/0
Extra: 01826b0f39bd27c1f3f5915cd5d33d75b7445b169de66a84228553dc209d90c5a2021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1011c1fc0b5eb628ae5e42419eb70f047737b01a12d8102de968d43c8e6a6fd6 0.600000000000 1368356 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": 911185, "vin": [ { "gen": { "height": 911175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1011c1fc0b5eb628ae5e42419eb70f047737b01a12d8102de968d43c8e6a6fd6" } } ], "extra": [ 1, 130, 107, 15, 57, 189, 39, 193, 243, 245, 145, 92, 213, 211, 61, 117, 183, 68, 91, 22, 157, 230, 106, 132, 34, 133, 83, 220, 32, 157, 144, 197, 162, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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