Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aafc2e799e8b2998ec7726e0dee3ec85220f7bbc164ba5d46bf3fe12091ced1d

Tx prefix hash: 56760a0f2bbe8b9e75c4e16f1b1b7a288f6f3b7aa2f5a7f26ca000dccfb71b50
Tx public key: 47f222cd56c7602447f168343d9483777acc6cb76831d9780d449d62e8d1f122
Timestamp: 1726149835 Timestamp [UCT]: 2024-09-12 14:03:55 Age [y:d:h:m:s]: 01:027:01:35:44
Block: 1108531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277721 RingCT/type: yes/0
Extra: 0147f222cd56c7602447f168343d9483777acc6cb76831d9780d449d62e8d1f12202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1d57876265b9e880d0d22ef0bf7f4cbd4ab20aac9c55dcf0407424e93c1b73 0.600000000000 1586460 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": 1108541, "vin": [ { "gen": { "height": 1108531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1d57876265b9e880d0d22ef0bf7f4cbd4ab20aac9c55dcf0407424e93c1b73" } } ], "extra": [ 1, 71, 242, 34, 205, 86, 199, 96, 36, 71, 241, 104, 52, 61, 148, 131, 119, 122, 204, 108, 183, 104, 49, 217, 120, 13, 68, 157, 98, 232, 209, 241, 34, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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