Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f837dd27a0547ac45a13ebbf542471792ee09beabef5a5149e840087a41fdf

Tx prefix hash: f7cbc0a6c8de4f874ce8900351a844326194d6d5b9c79154196f2fe8224f53a7
Tx public key: 03a498f2e22e14ede0f94282d4c4c2c943feada78236f6f4bfc4901d5a342a52
Timestamp: 1702868925 Timestamp [UCT]: 2023-12-18 03:08:45 Age [y:d:h:m:s]: 01:335:19:14:41
Block: 915527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498857 RingCT/type: yes/0
Extra: 0103a498f2e22e14ede0f94282d4c4c2c943feada78236f6f4bfc4901d5a342a5202110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0a0506629efd72666e00429f3cef08ea3eeb03a20399e2a43631ad46ab5c880 0.600000000000 1372923 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": 915537, "vin": [ { "gen": { "height": 915527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0a0506629efd72666e00429f3cef08ea3eeb03a20399e2a43631ad46ab5c880" } } ], "extra": [ 1, 3, 164, 152, 242, 226, 46, 20, 237, 224, 249, 66, 130, 212, 196, 194, 201, 67, 254, 173, 167, 130, 54, 246, 244, 191, 196, 144, 29, 90, 52, 42, 82, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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