Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd5a996ca1b8f5a1f6ff5522464ab8b35a48842d8d4da52329106e97217871c

Tx prefix hash: dd530ff6bd7ef56630e681dc94012ef9ef4934eabd092c594465998c64f5ceac
Tx public key: 2e8c6879041292e34ace2036d92a2f58ebd1ff279b22bdfa9b71ae9b94e380eb
Timestamp: 1721220301 Timestamp [UCT]: 2024-07-17 12:45:01 Age [y:d:h:m:s]: 00:332:16:42:47
Block: 1067687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237636 RingCT/type: yes/0
Extra: 012e8c6879041292e34ace2036d92a2f58ebd1ff279b22bdfa9b71ae9b94e380eb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62acb62d1f5a273adb24c126dd87a8c4047b389d1aa51b9647a985bfc5f5bef0 0.600000000000 1538564 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": 1067697, "vin": [ { "gen": { "height": 1067687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62acb62d1f5a273adb24c126dd87a8c4047b389d1aa51b9647a985bfc5f5bef0" } } ], "extra": [ 1, 46, 140, 104, 121, 4, 18, 146, 227, 74, 206, 32, 54, 217, 42, 47, 88, 235, 209, 255, 39, 155, 34, 189, 250, 155, 113, 174, 155, 148, 227, 128, 235, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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