Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4adbe6d1a09142c154e6b9d496b1bf82ac44e6e7a0c2c8fd748ceec5491ae3ec

Tx prefix hash: 78f499269d4569cb308798a001a32fcd5d1bb80a64a862ff1785829be905d425
Tx public key: 8a7cec5dd0b2c9c116721c47572320a7c159a8809b32bc730aafd01e4d214183
Timestamp: 1709915474 Timestamp [UCT]: 2024-03-08 16:31:14 Age [y:d:h:m:s]: 01:070:12:34:32
Block: 973957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311427 RingCT/type: yes/0
Extra: 018a7cec5dd0b2c9c116721c47572320a7c159a8809b32bc730aafd01e4d21418302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d220497b41bf39b6d55fb2775fc4479004318254494a26cfb8235e4ad8851f9 0.600000000000 1433900 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": 973967, "vin": [ { "gen": { "height": 973957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d220497b41bf39b6d55fb2775fc4479004318254494a26cfb8235e4ad8851f9" } } ], "extra": [ 1, 138, 124, 236, 93, 208, 178, 201, 193, 22, 114, 28, 71, 87, 35, 32, 167, 193, 89, 168, 128, 155, 50, 188, 115, 10, 175, 208, 30, 77, 33, 65, 131, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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