Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02c949f43f1f41cc7ec90440b8f720069e23a05cb502a57ac2de3f6313dddf49

Tx prefix hash: 7a23bac6fb952865691a8f111f248b59ca8f293f5d942f77599fda1f0ecf808a
Tx public key: 15b67f9788fc40321f5db61ea0ef82394ec3b533e38310d4436f6cd8dbda00ca
Timestamp: 1581242444 Timestamp [UCT]: 2020-02-09 10:00:44 Age [y:d:h:m:s]: 04:364:06:15:15
Block: 61188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152290 RingCT/type: yes/0
Extra: 0115b67f9788fc40321f5db61ea0ef82394ec3b533e38310d4436f6cd8dbda00ca02110000004f03d36d11000000000000000000

1 output(s) for total of 384.828366330000 dcy

stealth address amount amount idx
00: 8a9bd24c88579c0c55aea7bb68201709c0baae1c846a87cfdaea7f4af92de23c 384.828366330000 112764 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": 61198, "vin": [ { "gen": { "height": 61188 } } ], "vout": [ { "amount": 384828366330, "target": { "key": "8a9bd24c88579c0c55aea7bb68201709c0baae1c846a87cfdaea7f4af92de23c" } } ], "extra": [ 1, 21, 182, 127, 151, 136, 252, 64, 50, 31, 93, 182, 30, 160, 239, 130, 57, 78, 195, 181, 51, 227, 131, 16, 212, 67, 111, 108, 216, 219, 218, 0, 202, 2, 17, 0, 0, 0, 79, 3, 211, 109, 17, 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