Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff584ebc59dfba109b3bec0f5298ca0044bcc59e591915c61b4cb56e9d4131f

Tx prefix hash: c3f2820fec5d7cdbc1ea7860b65f30716ff62ae0cfcf0ad85ef8f0eb2549f33e
Tx public key: 1e4eb20b33d16da1afe8630274f71b7a635a6c6ba0f12c6d16e66b496f1e9255
Timestamp: 1710090291 Timestamp [UCT]: 2024-03-10 17:04:51 Age [y:d:h:m:s]: 01:068:19:01:15
Block: 975412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310170 RingCT/type: yes/0
Extra: 011e4eb20b33d16da1afe8630274f71b7a635a6c6ba0f12c6d16e66b496f1e92550211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428072b6ba0ddee62562e683680673894dbfac7af5a85cd0066ed329651f7336 0.600000000000 1435383 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": 975422, "vin": [ { "gen": { "height": 975412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428072b6ba0ddee62562e683680673894dbfac7af5a85cd0066ed329651f7336" } } ], "extra": [ 1, 30, 78, 178, 11, 51, 209, 109, 161, 175, 232, 99, 2, 116, 247, 27, 122, 99, 90, 108, 107, 160, 241, 44, 109, 22, 230, 107, 73, 111, 30, 146, 85, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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