Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fed0b938fae9e023b01a879933b754fbe33d65304d550ba91f8ace736bc1b2ce

Tx prefix hash: b3d96f6d5f3198e70ec74e4a518bcafa95a9207a57fe70a14c79ffe06d47af4e
Tx public key: 276b5954f811cf9343c495187c92e9146057c6368d35e29e6272e1a70fd942d7
Timestamp: 1702751233 Timestamp [UCT]: 2023-12-16 18:27:13 Age [y:d:h:m:s]: 01:112:19:30:58
Block: 914556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341754 RingCT/type: yes/0
Extra: 01276b5954f811cf9343c495187c92e9146057c6368d35e29e6272e1a70fd942d7021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9acaa8090ce0fed2883504a7f622b5eab607c7a0bb8b1c952bfc7f3e0d365f 0.600000000000 1371886 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": 914566, "vin": [ { "gen": { "height": 914556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9acaa8090ce0fed2883504a7f622b5eab607c7a0bb8b1c952bfc7f3e0d365f" } } ], "extra": [ 1, 39, 107, 89, 84, 248, 17, 207, 147, 67, 196, 149, 24, 124, 146, 233, 20, 96, 87, 198, 54, 141, 53, 226, 158, 98, 114, 225, 167, 15, 217, 66, 215, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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