Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 278a8165720a81e7b112ddd1c714640e36615d2efb4723a2f49c546793e710df

Tx prefix hash: 2cd5cdaa7b71809cff8bd14b0df841f5156a7720cba0a0f2caffac4982e10e64
Tx public key: 86093494e4b77841b4550802d118b356c0a7e6b8db8705a7c153a924a6b0f3b1
Timestamp: 1712811615 Timestamp [UCT]: 2024-04-11 05:00:15 Age [y:d:h:m:s]: 00:274:07:27:30
Block: 997935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196369 RingCT/type: yes/0
Extra: 0186093494e4b77841b4550802d118b356c0a7e6b8db8705a7c153a924a6b0f3b102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80018f3f532dcae13f83fdd88aaa0b0bd90325e9b0ecae60d5b1d5ca66c750fb 0.600000000000 1458369 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": 997945, "vin": [ { "gen": { "height": 997935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80018f3f532dcae13f83fdd88aaa0b0bd90325e9b0ecae60d5b1d5ca66c750fb" } } ], "extra": [ 1, 134, 9, 52, 148, 228, 183, 120, 65, 180, 85, 8, 2, 209, 24, 179, 86, 192, 167, 230, 184, 219, 135, 5, 167, 193, 83, 169, 36, 166, 176, 243, 177, 2, 17, 0, 0, 0, 1, 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