Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd91dc212d528c2af21f15aae2dffadfb31697298e41fa47292db55f27f37792

Tx prefix hash: db67258ea4848d1c65dae1fa35ad3e55a4e27c347c143d920e37cc1806edab1c
Tx public key: 94bb715ace75df555fc07cb06bbc8d54ed039c6e00d46fbcb3b424d36aaa54df
Timestamp: 1649862328 Timestamp [UCT]: 2022-04-13 15:05:28 Age [y:d:h:m:s]: 02:299:17:28:29
Block: 479374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733859 RingCT/type: yes/0
Extra: 0194bb715ace75df555fc07cb06bbc8d54ed039c6e00d46fbcb3b424d36aaa54df021100000015c9067537000000000000000000

1 output(s) for total of 15.835623809000 dcy

stealth address amount amount idx
00: 1c3dd506092dee84d3506adbdf13d4b9c582796eba7a07dbbe0e5e660ea41241 15.835623809000 900251 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": 479384, "vin": [ { "gen": { "height": 479374 } } ], "vout": [ { "amount": 15835623809, "target": { "key": "1c3dd506092dee84d3506adbdf13d4b9c582796eba7a07dbbe0e5e660ea41241" } } ], "extra": [ 1, 148, 187, 113, 90, 206, 117, 223, 85, 95, 192, 124, 176, 107, 188, 141, 84, 237, 3, 156, 110, 0, 212, 111, 188, 179, 180, 36, 211, 106, 170, 84, 223, 2, 17, 0, 0, 0, 21, 201, 6, 117, 55, 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