Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576fa8571c0e0cbbcdf99b71be12e73677f048387efb589ea454331250cf8237

Tx prefix hash: bc71d3c4bb83d1e426f8d54c19505b7877472c53521df1639f2ef9f524839c14
Tx public key: 7597f5f5611a25489d74780dcbe0a129363476cfa3c037a6e876d684013a5a59
Timestamp: 1723083720 Timestamp [UCT]: 2024-08-08 02:22:00 Age [y:d:h:m:s]: 00:245:20:42:35
Block: 1083118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175608 RingCT/type: yes/0
Extra: 017597f5f5611a25489d74780dcbe0a129363476cfa3c037a6e876d684013a5a59021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86b5f6871be2d6c2ea71e4f7d95e120dfe2325897f6c4f45fa6e8aa18935760f 0.600000000000 1556953 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": 1083128, "vin": [ { "gen": { "height": 1083118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86b5f6871be2d6c2ea71e4f7d95e120dfe2325897f6c4f45fa6e8aa18935760f" } } ], "extra": [ 1, 117, 151, 245, 245, 97, 26, 37, 72, 157, 116, 120, 13, 203, 224, 161, 41, 54, 52, 118, 207, 163, 192, 55, 166, 232, 118, 214, 132, 1, 58, 90, 89, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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