Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7098899b305612d33ce2414d799e460a4c4c1b141d71ba3798d49b4d827cb7

Tx prefix hash: c71961abb40ed94fc392a5ae6a303cf1960894622a494abf4a61dd57a8007a19
Tx public key: f97f5da9aef4e6c5bc1702f48cf7f4e6c1094fdd26ef96f0ffdc96940acbce88
Timestamp: 1726402090 Timestamp [UCT]: 2024-09-15 12:08:10 Age [y:d:h:m:s]: 00:181:21:40:34
Block: 1110635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129838 RingCT/type: yes/0
Extra: 01f97f5da9aef4e6c5bc1702f48cf7f4e6c1094fdd26ef96f0ffdc96940acbce88021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bf0407ca7884c8f213abaf6a1fef5ee13b5aa8f1d0c0807e306070a1c619478 0.600000000000 1589310 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": 1110645, "vin": [ { "gen": { "height": 1110635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bf0407ca7884c8f213abaf6a1fef5ee13b5aa8f1d0c0807e306070a1c619478" } } ], "extra": [ 1, 249, 127, 93, 169, 174, 244, 230, 197, 188, 23, 2, 244, 140, 247, 244, 230, 193, 9, 79, 221, 38, 239, 150, 240, 255, 220, 150, 148, 10, 203, 206, 136, 2, 17, 0, 0, 0, 3, 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