Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e25dadcb642ee3d12aa577c22a6ec3c660c029f2fd55bf3d3364cf59135a3e1

Tx prefix hash: 0bf94f43358aa0b8e503104fedd07f5fe8e8ffa6b5f44c6208a75b53361114e4
Tx public key: 8e582fa67857e5b2dfa83ad704f7e89ed9a210d30cf43e6aac7bc0c200581e9a
Timestamp: 1685078910 Timestamp [UCT]: 2023-05-26 05:28:30 Age [y:d:h:m:s]: 01:326:07:40:26
Block: 768289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494438 RingCT/type: yes/0
Extra: 018e582fa67857e5b2dfa83ad704f7e89ed9a210d30cf43e6aac7bc0c200581e9a02110000000333af99f4000000000000000000

1 output(s) for total of 1.747188600000 dcy

stealth address amount amount idx
00: b1a0c8c9d9168e466506700854624190f88dc7cc3ca687e591f384b09986cc42 1.747188600000 1217482 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": 768299, "vin": [ { "gen": { "height": 768289 } } ], "vout": [ { "amount": 1747188600, "target": { "key": "b1a0c8c9d9168e466506700854624190f88dc7cc3ca687e591f384b09986cc42" } } ], "extra": [ 1, 142, 88, 47, 166, 120, 87, 229, 178, 223, 168, 58, 215, 4, 247, 232, 158, 217, 162, 16, 211, 12, 244, 62, 106, 172, 123, 192, 194, 0, 88, 30, 154, 2, 17, 0, 0, 0, 3, 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