Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc06f1d7fed3605e8e6661fe342c413955f74e112dcf4b3c2ba939300cc47c66

Tx prefix hash: cac8cea15f56f247667c2e3cc34a738699d1ac29ff2c5cf5b6e739718d42f6ab
Tx public key: fd5b6dad2ef67a1f77d2d7d565fc9575854cb8b55d673ab4483c083d788cd382
Timestamp: 1709418305 Timestamp [UCT]: 2024-03-02 22:25:05 Age [y:d:h:m:s]: 01:105:05:39:51
Block: 969835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336158 RingCT/type: yes/0
Extra: 01fd5b6dad2ef67a1f77d2d7d565fc9575854cb8b55d673ab4483c083d788cd3820211000000130011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbbc2a9d6e6c0ce49062b158d2b74eb78f1b64661c28b04e4eb66e573a9fe64e 0.600000000000 1429684 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": 969845, "vin": [ { "gen": { "height": 969835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbbc2a9d6e6c0ce49062b158d2b74eb78f1b64661c28b04e4eb66e573a9fe64e" } } ], "extra": [ 1, 253, 91, 109, 173, 46, 246, 122, 31, 119, 210, 215, 213, 101, 252, 149, 117, 133, 76, 184, 181, 93, 103, 58, 180, 72, 60, 8, 61, 120, 140, 211, 130, 2, 17, 0, 0, 0, 19, 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