Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6154f519eb22df3bbbf8cd8bef27fd1e5414ec1a65d41701819550b9910ab72

Tx prefix hash: 95bce3e5558297ce37de2b2a8f779172aba5b035eccdb892dc47e9f514a7b453
Tx public key: 1ec8ed19c8f25d165685a0e9116a7e0f5aabc248107558d80a331e98186c1144
Timestamp: 1719078660 Timestamp [UCT]: 2024-06-22 17:51:00 Age [y:d:h:m:s]: 00:267:18:38:28
Block: 1049901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191368 RingCT/type: yes/0
Extra: 011ec8ed19c8f25d165685a0e9116a7e0f5aabc248107558d80a331e98186c1144021100000009c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee7f54a4492ce30f0a857b6a995ddf6ec5ed1426ae342bd0700ce87d3b9a1cf5 0.600000000000 1520010 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": 1049911, "vin": [ { "gen": { "height": 1049901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee7f54a4492ce30f0a857b6a995ddf6ec5ed1426ae342bd0700ce87d3b9a1cf5" } } ], "extra": [ 1, 30, 200, 237, 25, 200, 242, 93, 22, 86, 133, 160, 233, 17, 106, 126, 15, 90, 171, 194, 72, 16, 117, 88, 216, 10, 51, 30, 152, 24, 108, 17, 68, 2, 17, 0, 0, 0, 9, 197, 249, 207, 208, 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