Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d407bfe5f61735619890cf38b2f78746e4d61909c5e6303e2ebc507aedb2f1d

Tx prefix hash: 3c7b3bbc9e916c1ef6acd47e84370939af5723aaf9b390035e4ff90e326f9336
Tx public key: 392ce8315945aaa64e65cf6530b4fce34b2bddc26ac62a3cc74ea9cea51f3922
Timestamp: 1715298525 Timestamp [UCT]: 2024-05-09 23:48:45 Age [y:d:h:m:s]: 00:250:05:00:39
Block: 1018576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179075 RingCT/type: yes/0
Extra: 01392ce8315945aaa64e65cf6530b4fce34b2bddc26ac62a3cc74ea9cea51f392202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38bbfc5dc72f5fb14fa4ca51d3d7c6afce99d9b8b82f608a312bf2e0aa096b85 0.600000000000 1482369 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": 1018586, "vin": [ { "gen": { "height": 1018576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bbfc5dc72f5fb14fa4ca51d3d7c6afce99d9b8b82f608a312bf2e0aa096b85" } } ], "extra": [ 1, 57, 44, 232, 49, 89, 69, 170, 166, 78, 101, 207, 101, 48, 180, 252, 227, 75, 43, 221, 194, 106, 198, 42, 60, 199, 78, 169, 206, 165, 31, 57, 34, 2, 17, 0, 0, 0, 3, 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