Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52bcb8b53bf80762db97f2ab2b9d0f5c1e579c09f91a460f8fc2e20c9d666705

Tx prefix hash: 663e84657cf308cd0e6b89a0d959da9947a52155540a88dcb2d5d6469df47906
Tx public key: e7df1d59fa7414cf8a2ae3c9650178930e7f354d303dfcd1b9208a66a7bfc6cf
Timestamp: 1697441786 Timestamp [UCT]: 2023-10-16 07:36:26 Age [y:d:h:m:s]: 01:209:20:18:34
Block: 870735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411027 RingCT/type: yes/0
Extra: 01e7df1d59fa7414cf8a2ae3c9650178930e7f354d303dfcd1b9208a66a7bfc6cf021100000005faf35c9c000000000000000000

1 output(s) for total of 0.799638161000 dcy

stealth address amount amount idx
00: 2222ab511d4a2aa4325a99d3af4997f44dc32c69bc61f26fa57debc7702029c8 0.799638161000 1325618 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": 870745, "vin": [ { "gen": { "height": 870735 } } ], "vout": [ { "amount": 799638161, "target": { "key": "2222ab511d4a2aa4325a99d3af4997f44dc32c69bc61f26fa57debc7702029c8" } } ], "extra": [ 1, 231, 223, 29, 89, 250, 116, 20, 207, 138, 42, 227, 201, 101, 1, 120, 147, 14, 127, 53, 77, 48, 61, 252, 209, 185, 32, 138, 102, 167, 191, 198, 207, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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