Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3c1913bb198df0001d41a5e9f41d3c9ff744d298d754db83cb8228ff17a129

Tx prefix hash: 681db3e317809b23b0e81fcf288108a7375b543d5c38c1a16635208dc9698f1b
Tx public key: 0885dd5d74d52b439ae97c4e72b64c71232e64e953f83d0e2bb9ae76f55c54c1
Timestamp: 1650034532 Timestamp [UCT]: 2022-04-15 14:55:32 Age [y:d:h:m:s]: 02:254:13:30:53
Block: 480774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701862 RingCT/type: yes/0
Extra: 010885dd5d74d52b439ae97c4e72b64c71232e64e953f83d0e2bb9ae76f55c54c1021100000001a8c141c5000000000000000000

1 output(s) for total of 15.667380573000 dcy

stealth address amount amount idx
00: 0b4e1e7e4eceaabaafb34c2c00e681a7d7ff5fd6c07903dbf2ca02a3e94e7435 15.667380573000 901873 of 0

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": 480784, "vin": [ { "gen": { "height": 480774 } } ], "vout": [ { "amount": 15667380573, "target": { "key": "0b4e1e7e4eceaabaafb34c2c00e681a7d7ff5fd6c07903dbf2ca02a3e94e7435" } } ], "extra": [ 1, 8, 133, 221, 93, 116, 213, 43, 67, 154, 233, 124, 78, 114, 182, 76, 113, 35, 46, 100, 233, 83, 248, 61, 14, 43, 185, 174, 118, 245, 92, 84, 193, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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