Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377d6399b840836aad320dc992657b6c136bd3d01c92526840989cb9838a8b99

Tx prefix hash: 35ba43e7af30f5aabd419c4537385ac5924d0b0c9ea5d781f60cd0ff85e3682c
Tx public key: 36d032fa2409810959d84385aa7ca35a38e7ed89057c8d1095f25f7f57884a92
Timestamp: 1694503526 Timestamp [UCT]: 2023-09-12 07:25:26 Age [y:d:h:m:s]: 01:204:05:43:35
Block: 846363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407062 RingCT/type: yes/0
Extra: 0136d032fa2409810959d84385aa7ca35a38e7ed89057c8d1095f25f7f57884a92021100000002faf35c9c000000000000000000

1 output(s) for total of 0.963048371000 dcy

stealth address amount amount idx
00: 8e42430d800c0e88dbbf69f0fdc3affc3d2d4350b02b632a03594262b2ae0ef7 0.963048371000 1299819 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": 846373, "vin": [ { "gen": { "height": 846363 } } ], "vout": [ { "amount": 963048371, "target": { "key": "8e42430d800c0e88dbbf69f0fdc3affc3d2d4350b02b632a03594262b2ae0ef7" } } ], "extra": [ 1, 54, 208, 50, 250, 36, 9, 129, 9, 89, 216, 67, 133, 170, 124, 163, 90, 56, 231, 237, 137, 5, 124, 141, 16, 149, 242, 95, 127, 87, 136, 74, 146, 2, 17, 0, 0, 0, 2, 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