Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1399e5893cee9fcbffee95769fe068ca051ed5ee6154b6a6ced7370c15b8fc74

Tx prefix hash: 17c6fb7c9b6205b8cbe023965390b20a0836ec408a04be72553b9eeb08b4f99b
Tx public key: c134247de20e77413f2d29469e6c8bb0f9c5df8ccbf1970f04f645ae15be32b2
Timestamp: 1713343575 Timestamp [UCT]: 2024-04-17 08:46:15 Age [y:d:h:m:s]: 00:336:01:28:57
Block: 1002364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240274 RingCT/type: yes/0
Extra: 01c134247de20e77413f2d29469e6c8bb0f9c5df8ccbf1970f04f645ae15be32b202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc322cbf512989c9be0e90b13137c52bfa6e4ff2660dc2b85f4b6228b6f36ea5 0.600000000000 1462880 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": 1002374, "vin": [ { "gen": { "height": 1002364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc322cbf512989c9be0e90b13137c52bfa6e4ff2660dc2b85f4b6228b6f36ea5" } } ], "extra": [ 1, 193, 52, 36, 125, 226, 14, 119, 65, 63, 45, 41, 70, 158, 108, 139, 176, 249, 197, 223, 140, 203, 241, 151, 15, 4, 246, 69, 174, 21, 190, 50, 178, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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