Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047b06f20fc0af03e1a53556eeab5309e7202faa47b72c72d48eb72f534a6576

Tx prefix hash: 6bd6edefe0a7eae2d8424cdf74b4b5a11469588ab5aec2e523541a69efb7f0c0
Tx public key: b63c9367b0ecb2fd0a2695dbf74fca922da62b921cee2b43034881a027a60572
Timestamp: 1635300645 Timestamp [UCT]: 2021-10-27 02:10:45 Age [y:d:h:m:s]: 03:139:10:27:24
Block: 361256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877876 RingCT/type: yes/0
Extra: 01b63c9367b0ecb2fd0a2695dbf74fca922da62b921cee2b43034881a027a6057202110000000c6e80e2c6000000000000000000

1 output(s) for total of 38.995035011000 dcy

stealth address amount amount idx
00: e1467dfa98d78cfe9bf11e1b3077a2e71d0dce34ea4d1c76a0e18217557bb361 38.995035011000 735033 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": 361266, "vin": [ { "gen": { "height": 361256 } } ], "vout": [ { "amount": 38995035011, "target": { "key": "e1467dfa98d78cfe9bf11e1b3077a2e71d0dce34ea4d1c76a0e18217557bb361" } } ], "extra": [ 1, 182, 60, 147, 103, 176, 236, 178, 253, 10, 38, 149, 219, 247, 79, 202, 146, 45, 166, 43, 146, 28, 238, 43, 67, 3, 72, 129, 160, 39, 166, 5, 114, 2, 17, 0, 0, 0, 12, 110, 128, 226, 198, 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