Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d95f8b17f58cbedf328df945ed5102e8d74d696dde16de24c850673414b03d

Tx prefix hash: 5fcbe067b0ce6af83f593883a643e026d36dd26996d70d0e204c949d736b25c0
Tx public key: c9bff8aed5a113b7de8ea10ebe174228e02e37df8fefd9336fe64fae18c07d3a
Timestamp: 1707775033 Timestamp [UCT]: 2024-02-12 21:57:13 Age [y:d:h:m:s]: 01:053:14:24:28
Block: 956197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299346 RingCT/type: yes/0
Extra: 01c9bff8aed5a113b7de8ea10ebe174228e02e37df8fefd9336fe64fae18c07d3a021100000001b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9982534b862a47ae2fd164efa21d95f4aa883480eff81799e78ab40e45590f4 0.600000000000 1415501 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": 956207, "vin": [ { "gen": { "height": 956197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9982534b862a47ae2fd164efa21d95f4aa883480eff81799e78ab40e45590f4" } } ], "extra": [ 1, 201, 191, 248, 174, 213, 161, 19, 183, 222, 142, 161, 14, 190, 23, 66, 40, 224, 46, 55, 223, 143, 239, 217, 51, 111, 230, 79, 174, 24, 192, 125, 58, 2, 17, 0, 0, 0, 1, 182, 226, 220, 51, 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