Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b0de9cd41bfbbdccbc276cd2bfcd3160d7e16e7136ac1779200e7038406a23

Tx prefix hash: c7977525c2dc7e3fa82a7a9f1a6e553bc07d2caaccc6f675ead2faf30a933aef
Tx public key: 4d4077dcc41873e8bada6ecad8a3eda07abef12d2e0bb773e3c87d79fd072848
Timestamp: 1713276173 Timestamp [UCT]: 2024-04-16 14:02:53 Age [y:d:h:m:s]: 01:012:00:27:37
Block: 1001789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269573 RingCT/type: yes/0
Extra: 014d4077dcc41873e8bada6ecad8a3eda07abef12d2e0bb773e3c87d79fd07284802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87d7138db4319acc9edd8f6213e3d7add3b5c29592d07dfbb7e9474682055d3f 0.600000000000 1462301 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": 1001799, "vin": [ { "gen": { "height": 1001789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87d7138db4319acc9edd8f6213e3d7add3b5c29592d07dfbb7e9474682055d3f" } } ], "extra": [ 1, 77, 64, 119, 220, 196, 24, 115, 232, 186, 218, 110, 202, 216, 163, 237, 160, 122, 190, 241, 45, 46, 11, 183, 115, 227, 200, 125, 121, 253, 7, 40, 72, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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