Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e2044a06e940813677b76e4cad7f17071a4440772e6ea9364c6f76c685005f

Tx prefix hash: 3692614dff5a551991b80841c3ee0ab78d60a10c56ad407c9f54d9b75ca3c052
Tx public key: e83c642150fb50b041bdb79bb60e80d26b30115dee9ef2a1d587c8c2871c5b38
Timestamp: 1708828993 Timestamp [UCT]: 2024-02-25 02:43:13 Age [y:d:h:m:s]: 01:040:13:20:07
Block: 964946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289997 RingCT/type: yes/0
Extra: 01e83c642150fb50b041bdb79bb60e80d26b30115dee9ef2a1d587c8c2871c5b380211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a9d3a02dde04b6e76bbc48e472065d1b4895f30f3d4a60d352b836e4df91b55 0.600000000000 1424689 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": 964956, "vin": [ { "gen": { "height": 964946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a9d3a02dde04b6e76bbc48e472065d1b4895f30f3d4a60d352b836e4df91b55" } } ], "extra": [ 1, 232, 60, 100, 33, 80, 251, 80, 176, 65, 189, 183, 155, 182, 14, 128, 210, 107, 48, 17, 93, 238, 158, 242, 161, 213, 135, 200, 194, 135, 28, 91, 56, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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