Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04263f6bd9105f10cdb36f1d7e50826f11202c24481a1c78e65e588780d1d3b1

Tx prefix hash: 980a4770d2046a7fb1f5229176e687709445b7c06dfffb8afc49826daeafe486
Tx public key: c384327e6caa395ab81e74f58fceb8f8dbc1ef0b7ecf34e1d194cd3fc6f0cd77
Timestamp: 1731967221 Timestamp [UCT]: 2024-11-18 22:00:21 Age [y:d:h:m:s]: 00:005:03:48:39
Block: 1156676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3701 RingCT/type: yes/0
Extra: 01c384327e6caa395ab81e74f58fceb8f8dbc1ef0b7ecf34e1d194cd3fc6f0cd770211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82fe454dd686059d8bfff276df6814d99229956ef82ebe8aee29eb674e8a4e63 0.600000000000 1642299 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": 1156686, "vin": [ { "gen": { "height": 1156676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82fe454dd686059d8bfff276df6814d99229956ef82ebe8aee29eb674e8a4e63" } } ], "extra": [ 1, 195, 132, 50, 126, 108, 170, 57, 90, 184, 30, 116, 245, 143, 206, 184, 248, 219, 193, 239, 11, 126, 207, 52, 225, 209, 148, 205, 63, 198, 240, 205, 119, 2, 17, 0, 0, 0, 2, 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