Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2003353703ee00e5894e8f26134381a5e0fe2e211f0ec55abbd4b7263c796e1

Tx prefix hash: ea7a5986951b70a74f9b8f857067fa8ded679e578bcc6725503ba1bda50f83aa
Tx public key: 837fa6047133d83e82a0ef1d29dd63af3d3f1d612bc40c81d6ac4a2a11ec852f
Timestamp: 1725646919 Timestamp [UCT]: 2024-09-06 18:21:59 Age [y:d:h:m:s]: 00:236:15:36:18
Block: 1104373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168978 RingCT/type: yes/0
Extra: 01837fa6047133d83e82a0ef1d29dd63af3d3f1d612bc40c81d6ac4a2a11ec852f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 650f781b3ec7de66d95ecfc7b76919bc57a49e49a460df31c68281d64cef484e 0.600000000000 1581490 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": 1104383, "vin": [ { "gen": { "height": 1104373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "650f781b3ec7de66d95ecfc7b76919bc57a49e49a460df31c68281d64cef484e" } } ], "extra": [ 1, 131, 127, 166, 4, 113, 51, 216, 62, 130, 160, 239, 29, 41, 221, 99, 175, 61, 63, 29, 97, 43, 196, 12, 129, 214, 172, 74, 42, 17, 236, 133, 47, 2, 17, 0, 0, 0, 2, 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