Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2e8a44068a7358f5848467fd60680d71e6983ebd364acd8c8a9484fdb5f485

Tx prefix hash: f9858add2325c1c1ec4748e7427d4f61569f3f1c463d8e848347bdf1d1d60d4b
Tx public key: 39fa88952f6c946ed3caf793f7b6029126ca489a51004b027931a59c7d7bd411
Timestamp: 1736560116 Timestamp [UCT]: 2025-01-11 01:48:36 Age [y:d:h:m:s]: 00:067:09:12:38
Block: 1194698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47964 RingCT/type: yes/0
Extra: 0139fa88952f6c946ed3caf793f7b6029126ca489a51004b027931a59c7d7bd411021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4caae5c16a789b38653506626f8b60a25efad9d0ae7aaf3794b5c4ab127f3fe3 0.600000000000 1681275 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": 1194708, "vin": [ { "gen": { "height": 1194698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4caae5c16a789b38653506626f8b60a25efad9d0ae7aaf3794b5c4ab127f3fe3" } } ], "extra": [ 1, 57, 250, 136, 149, 47, 108, 148, 110, 211, 202, 247, 147, 247, 182, 2, 145, 38, 202, 72, 154, 81, 0, 75, 2, 121, 49, 165, 156, 125, 123, 212, 17, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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