Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7b210a4237173fa173e934d13e6ef9fff7992e3a7d067906e94817c29476ae

Tx prefix hash: 1f414761f93bb5603c733c67cf5f961560e1ec1e2803e1cba917914e9d6d04a8
Tx public key: ad23217a1586dc0590c93c49cb55fdefd9d842e6d5fd8c0fac102e7719075228
Timestamp: 1705461948 Timestamp [UCT]: 2024-01-17 03:25:48 Age [y:d:h:m:s]: 01:092:12:07:04
Block: 936998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327239 RingCT/type: yes/0
Extra: 01ad23217a1586dc0590c93c49cb55fdefd9d842e6d5fd8c0fac102e771907522802110000007159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a9f57cbf83a54edcacab31337a030c83f31a6af517cc827f9493d524b209fe 0.600000000000 1395042 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": 937008, "vin": [ { "gen": { "height": 936998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a9f57cbf83a54edcacab31337a030c83f31a6af517cc827f9493d524b209fe" } } ], "extra": [ 1, 173, 35, 33, 122, 21, 134, 220, 5, 144, 201, 60, 73, 203, 85, 253, 239, 217, 216, 66, 230, 213, 253, 140, 15, 172, 16, 46, 119, 25, 7, 82, 40, 2, 17, 0, 0, 0, 113, 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