Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916683376ea3d793cfd1791b2f49ce7da2842a756a8092f5d825190ba537406f

Tx prefix hash: 2a7f3acf13dff56786bca5daabdc31c19ab6b17a4f1f3f157d795a8837b0d93f
Tx public key: d5db471ed0af5a9b92006ad7732fb45dff9fba8d59ff3f33acb0fcfca377e03e
Timestamp: 1711893390 Timestamp [UCT]: 2024-03-31 13:56:30 Age [y:d:h:m:s]: 01:046:10:19:59
Block: 990359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294162 RingCT/type: yes/0
Extra: 01d5db471ed0af5a9b92006ad7732fb45dff9fba8d59ff3f33acb0fcfca377e03e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3376484ccc22735c7d368f33851db24d40b4828fdf4ae54c858b24a5eb847225 0.600000000000 1450681 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": 990369, "vin": [ { "gen": { "height": 990359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3376484ccc22735c7d368f33851db24d40b4828fdf4ae54c858b24a5eb847225" } } ], "extra": [ 1, 213, 219, 71, 30, 208, 175, 90, 155, 146, 0, 106, 215, 115, 47, 180, 93, 255, 159, 186, 141, 89, 255, 63, 51, 172, 176, 252, 252, 163, 119, 224, 62, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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