Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 636ad7e1f36709e877e1190e6564dd184b0f5b0558b760d075c7e62ff4437a4c

Tx prefix hash: 86a156b50613d921d192a8ee87d5b1c88da9259fd553836d020d474353187081
Tx public key: 58bf832be4b4a0ec94ac5f0cb48c5fa0a6e07b2244303c9ad2f65d98eb927fc2
Timestamp: 1727982789 Timestamp [UCT]: 2024-10-03 19:13:09 Age [y:d:h:m:s]: 00:220:00:05:06
Block: 1123740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157052 RingCT/type: yes/0
Extra: 0158bf832be4b4a0ec94ac5f0cb48c5fa0a6e07b2244303c9ad2f65d98eb927fc202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f48992940f79a1828cd39188b72d7269bc81c0858095df1cf586eea62ec52836 0.600000000000 1606275 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": 1123750, "vin": [ { "gen": { "height": 1123740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f48992940f79a1828cd39188b72d7269bc81c0858095df1cf586eea62ec52836" } } ], "extra": [ 1, 88, 191, 131, 43, 228, 180, 160, 236, 148, 172, 95, 12, 180, 140, 95, 160, 166, 224, 123, 34, 68, 48, 60, 154, 210, 246, 93, 152, 235, 146, 127, 194, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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