Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86188de6bb1c231e338a48927f4ce727d9b1d99c6bd2532aed78d5c6342db7af

Tx prefix hash: 21ac62087af7e74e9012f29bc3cefa32d407418efa9658a41314d3ce06685615
Tx public key: 859a77f52450a7e00d710b7bd83445edf4c410e63740106b6e3c3b1f281c5390
Timestamp: 1730574701 Timestamp [UCT]: 2024-11-02 19:11:41 Age [y:d:h:m:s]: 00:166:19:35:49
Block: 1145138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119074 RingCT/type: yes/0
Extra: 01859a77f52450a7e00d710b7bd83445edf4c410e63740106b6e3c3b1f281c53900211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6aff81d2c0e7ac9162c374b3f2e6b09998483d707579fc7efb7d0adc92a1070 0.600000000000 1629533 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": 1145148, "vin": [ { "gen": { "height": 1145138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6aff81d2c0e7ac9162c374b3f2e6b09998483d707579fc7efb7d0adc92a1070" } } ], "extra": [ 1, 133, 154, 119, 245, 36, 80, 167, 224, 13, 113, 11, 123, 216, 52, 69, 237, 244, 196, 16, 230, 55, 64, 16, 107, 110, 60, 59, 31, 40, 28, 83, 144, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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