Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dfadc3ab87b3fd2d9d9f969a50cba02d65af3a9e29ef82420680383fbd90df1

Tx prefix hash: 97b5c7d475ca743050e3a03286cb981f25ef3ec4e034f48e082501270259ab79
Tx public key: 05d2e9b06d37aa757fe60256d2b1aae047ea33fa2eff2a29edd46fe9a7419ae8
Timestamp: 1673144790 Timestamp [UCT]: 2023-01-08 02:26:30 Age [y:d:h:m:s]: 01:313:07:25:09
Block: 669954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484934 RingCT/type: yes/0
Extra: 0105d2e9b06d37aa757fe60256d2b1aae047ea33fa2eff2a29edd46fe9a7419ae802110000000474b6d784000000000000000000

1 output(s) for total of 3.699680701000 dcy

stealth address amount amount idx
00: eba2de02a214f3cbdcd436ea258c7e6bb7e0f3c96429453172582f95a972b7b4 3.699680701000 1111321 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": 669964, "vin": [ { "gen": { "height": 669954 } } ], "vout": [ { "amount": 3699680701, "target": { "key": "eba2de02a214f3cbdcd436ea258c7e6bb7e0f3c96429453172582f95a972b7b4" } } ], "extra": [ 1, 5, 210, 233, 176, 109, 55, 170, 117, 127, 230, 2, 86, 210, 177, 170, 224, 71, 234, 51, 250, 46, 255, 42, 41, 237, 212, 111, 233, 167, 65, 154, 232, 2, 17, 0, 0, 0, 4, 116, 182, 215, 132, 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