Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45056028ee8941833c5fc4444b58f7681efbe03d2ff751fd058edebf446a6279

Tx prefix hash: fcf429a1e3716f78f148f7b6e8fb3e83c39b8a8a8c29c7d2aa2e50eba45ab753
Tx public key: 92e6fb4116486f107cc95c487ec32d3d0c43081771ec9245c6b307dc7c99c9d6
Timestamp: 1677786535 Timestamp [UCT]: 2023-03-02 19:48:55 Age [y:d:h:m:s]: 01:359:07:46:20
Block: 708468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517483 RingCT/type: yes/0
Extra: 0192e6fb4116486f107cc95c487ec32d3d0c43081771ec9245c6b307dc7c99c9d60211000000015029cbac000000000000000000

1 output(s) for total of 2.757727296000 dcy

stealth address amount amount idx
00: 6ea04f3eaa0b5ec8c839c9472d5b574267cf3899c55dbc8e429cd26432a2c5db 2.757727296000 1152363 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": 708478, "vin": [ { "gen": { "height": 708468 } } ], "vout": [ { "amount": 2757727296, "target": { "key": "6ea04f3eaa0b5ec8c839c9472d5b574267cf3899c55dbc8e429cd26432a2c5db" } } ], "extra": [ 1, 146, 230, 251, 65, 22, 72, 111, 16, 124, 201, 92, 72, 126, 195, 45, 61, 12, 67, 8, 23, 113, 236, 146, 69, 198, 179, 7, 220, 124, 153, 201, 214, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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