Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b8377f3eef8ad7a477a87cddfa234fb48232f41e780f0f7da90c81932ccf5e9

Tx prefix hash: b4f809643e32048c8c9de896a1a53d1261435514e3f70230a1513f5e88082c7c
Tx public key: e0d0d8a486317f3afeae2a4b797b8aaf883f62b336de481d589074cd5dff08eb
Timestamp: 1721485619 Timestamp [UCT]: 2024-07-20 14:26:59 Age [y:d:h:m:s]: 00:095:01:03:46
Block: 1069870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68052 RingCT/type: yes/0
Extra: 01e0d0d8a486317f3afeae2a4b797b8aaf883f62b336de481d589074cd5dff08eb021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98952368681f7b435d573857f6aa0628a4d749b5c11f41368d529e0027205fb4 0.600000000000 1541471 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": 1069880, "vin": [ { "gen": { "height": 1069870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98952368681f7b435d573857f6aa0628a4d749b5c11f41368d529e0027205fb4" } } ], "extra": [ 1, 224, 208, 216, 164, 134, 49, 127, 58, 254, 174, 42, 75, 121, 123, 138, 175, 136, 63, 98, 179, 54, 222, 72, 29, 88, 144, 116, 205, 93, 255, 8, 235, 2, 17, 0, 0, 0, 5, 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