Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eab0968145e64fd68bc1a3f488096e2c777867fd9116bcedd861f7b8b805a302

Tx prefix hash: af5a2a2cf4d43383c01598a7b85bf5890008cedce89ee793b4e6209de50feb74
Tx public key: 11b4f814f581fe8b7ea27b8b910925b6b6c9f4d1db3e5b476a771d69c782ed1e
Timestamp: 1730741970 Timestamp [UCT]: 2024-11-04 17:39:30 Age [y:d:h:m:s]: 00:153:08:04:59
Block: 1146521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109414 RingCT/type: yes/0
Extra: 0111b4f814f581fe8b7ea27b8b910925b6b6c9f4d1db3e5b476a771d69c782ed1e021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b068afdcd9bf4a58344515a3bcaf0fe06ada4d42e2a5f26e72c854a4fc5f273b 0.600000000000 1631178 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": 1146531, "vin": [ { "gen": { "height": 1146521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b068afdcd9bf4a58344515a3bcaf0fe06ada4d42e2a5f26e72c854a4fc5f273b" } } ], "extra": [ 1, 17, 180, 248, 20, 245, 129, 254, 139, 126, 162, 123, 139, 145, 9, 37, 182, 182, 201, 244, 209, 219, 62, 91, 71, 106, 119, 29, 105, 199, 130, 237, 30, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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