Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0951892d8b479a9acce7e5e5e20257d7d0ade80fbf122b04f12d87678bc4c58

Tx prefix hash: 41239add103ec406688693d063c31f9dae6673e2bdb2ac53985aed1d2186c7c0
Tx public key: 271d4fe2041872868089d10c91227d636a0c8d7dc9af51ffdce2e08d65c2eeab
Timestamp: 1709903091 Timestamp [UCT]: 2024-03-08 13:04:51 Age [y:d:h:m:s]: 00:229:09:22:19
Block: 973856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164276 RingCT/type: yes/0
Extra: 01271d4fe2041872868089d10c91227d636a0c8d7dc9af51ffdce2e08d65c2eeab0211000000013a93cea7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4923d5aee497e0652c7a8b851f8c0e2da6149763df9db000695c942a54a0d10 0.600000000000 1433797 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": 973866, "vin": [ { "gen": { "height": 973856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4923d5aee497e0652c7a8b851f8c0e2da6149763df9db000695c942a54a0d10" } } ], "extra": [ 1, 39, 29, 79, 226, 4, 24, 114, 134, 128, 137, 209, 12, 145, 34, 125, 99, 106, 12, 141, 125, 201, 175, 81, 255, 220, 226, 224, 141, 101, 194, 238, 171, 2, 17, 0, 0, 0, 1, 58, 147, 206, 167, 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