Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91c3260e4a7500ae2e9674133ac1a83750cb17eb4c4c89d3b4874f152e3a83e5

Tx prefix hash: 6a8dd023607a39eb17381e98caea09cc529c59deb4f7660800f87ede6d83748b
Tx public key: c8b0c959cb81b2b22a17c0097d4d60a605505643e05e8b667847cac3c7bccc23
Timestamp: 1750921445 Timestamp [UCT]: 2025-06-26 07:04:05 Age [y:d:h:m:s]: 00:145:16:12:41
Block: 1313016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102111 RingCT/type: yes/0
Extra: 01c8b0c959cb81b2b22a17c0097d4d60a605505643e05e8b667847cac3c7bccc230211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6065c7db2b7af6b032a751624b22d85d79c69063217dc61fabc1bb639211454 0.600000000000 1800653 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": 1313026, "vin": [ { "gen": { "height": 1313016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6065c7db2b7af6b032a751624b22d85d79c69063217dc61fabc1bb639211454" } } ], "extra": [ 1, 200, 176, 201, 89, 203, 129, 178, 178, 42, 23, 192, 9, 125, 77, 96, 166, 5, 80, 86, 67, 224, 94, 139, 102, 120, 71, 202, 195, 199, 188, 204, 35, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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