Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62f460ec2f43cfe37118bed898636d008acb5cb766af82090f5a452fbfdcc256

Tx prefix hash: 638fa28045eea9702ed6a1aa8256a4824409b84932ba1720a24bfad4a2cddbb3
Tx public key: 6c5b323bab58daa811bf9b8f2c9c59c744b3a7369533ab0b05b03682f88776ff
Timestamp: 1676055811 Timestamp [UCT]: 2023-02-10 19:03:31 Age [y:d:h:m:s]: 02:109:10:18:46
Block: 694120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599854 RingCT/type: yes/0
Extra: 016c5b323bab58daa811bf9b8f2c9c59c744b3a7369533ab0b05b03682f88776ff02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.076750069000 dcy

stealth address amount amount idx
00: 1f398fdc506e0a576559634f225b7e1e5c3a9125ae183beb5345a1a0c6e8b0f3 3.076750069000 1137035 of 0

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": 694130, "vin": [ { "gen": { "height": 694120 } } ], "vout": [ { "amount": 3076750069, "target": { "key": "1f398fdc506e0a576559634f225b7e1e5c3a9125ae183beb5345a1a0c6e8b0f3" } } ], "extra": [ 1, 108, 91, 50, 59, 171, 88, 218, 168, 17, 191, 155, 143, 44, 156, 89, 199, 68, 179, 167, 54, 149, 51, 171, 11, 5, 176, 54, 130, 248, 135, 118, 255, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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