Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cced7946f2d77c38724e6401df2340916fa67e5f2c6f666bcfad3ae1be6b925

Tx prefix hash: f444105cc0ca9a84de62c674249ba6f39f5ab2f1dffc6934fc018a8e630de4cb
Tx public key: 2a7dfc36e98c9a94ae6b5cd193ae81b629f7f466968968476013df7a2f3dc37c
Timestamp: 1700811720 Timestamp [UCT]: 2023-11-24 07:42:00 Age [y:d:h:m:s]: 01:057:11:16:44
Block: 898472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302459 RingCT/type: yes/0
Extra: 012a7dfc36e98c9a94ae6b5cd193ae81b629f7f466968968476013df7a2f3dc37c02110000000233af99f4000000000000000000

1 output(s) for total of 0.647126636000 dcy

stealth address amount amount idx
00: bbe2a895c7636ef5be2f391e9df09780688872c904cf0fc564e9370c253c1310 0.647126636000 1354889 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": 898482, "vin": [ { "gen": { "height": 898472 } } ], "vout": [ { "amount": 647126636, "target": { "key": "bbe2a895c7636ef5be2f391e9df09780688872c904cf0fc564e9370c253c1310" } } ], "extra": [ 1, 42, 125, 252, 54, 233, 140, 154, 148, 174, 107, 92, 209, 147, 174, 129, 182, 41, 247, 244, 102, 150, 137, 104, 71, 96, 19, 223, 122, 47, 61, 195, 124, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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