Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d026bc7b421f5cee40355047d5b82e3ae9267eac75ce34938940ccfd16306d6

Tx prefix hash: dee99af34a7bca3fb02f7442bcf75347762d2a0509eb9a6135f8fe2cee255da5
Tx public key: ab5da14380c4a21708aae4b951484779059f0e24d46b6040278db57edcdb8b1e
Timestamp: 1716236360 Timestamp [UCT]: 2024-05-20 20:19:20 Age [y:d:h:m:s]: 00:237:06:29:30
Block: 1026361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169802 RingCT/type: yes/0
Extra: 01ab5da14380c4a21708aae4b951484779059f0e24d46b6040278db57edcdb8b1e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa64ca8ddbf5d017adddb7c32f6687a374a1c894efbaaec2883dd7f42376f8b9 0.600000000000 1493400 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": 1026371, "vin": [ { "gen": { "height": 1026361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa64ca8ddbf5d017adddb7c32f6687a374a1c894efbaaec2883dd7f42376f8b9" } } ], "extra": [ 1, 171, 93, 161, 67, 128, 196, 162, 23, 8, 170, 228, 185, 81, 72, 71, 121, 5, 159, 14, 36, 212, 107, 96, 64, 39, 141, 181, 126, 220, 219, 139, 30, 2, 17, 0, 0, 0, 2, 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