Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d164f8f54086829db137509f59900dd1380b6075b33a7baf59612f1f30c9de3b

Tx prefix hash: f4b8d03639f6954f800c3ac1e321933a67ab9dc8c8f0f0b882adbfe8ea7101a5
Tx public key: f0df4081508e4f1166ca9829ca996f81ce100083b31eabc4a274e35a95124a4c
Timestamp: 1673165677 Timestamp [UCT]: 2023-01-08 08:14:37 Age [y:d:h:m:s]: 02:047:14:53:06
Block: 670132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555685 RingCT/type: yes/0
Extra: 01f0df4081508e4f1166ca9829ca996f81ce100083b31eabc4a274e35a95124a4c02110000000183600029000000000000000000

1 output(s) for total of 3.694659807000 dcy

stealth address amount amount idx
00: 1601a6c4f5db76260444d05c585068afe68d02a7f73d04df9bd38c6c19acf6a8 3.694659807000 1111505 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": 670142, "vin": [ { "gen": { "height": 670132 } } ], "vout": [ { "amount": 3694659807, "target": { "key": "1601a6c4f5db76260444d05c585068afe68d02a7f73d04df9bd38c6c19acf6a8" } } ], "extra": [ 1, 240, 223, 64, 129, 80, 142, 79, 17, 102, 202, 152, 41, 202, 153, 111, 129, 206, 16, 0, 131, 179, 30, 171, 196, 162, 116, 227, 90, 149, 18, 74, 76, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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