Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fd500bad55d0aa6207782a6693c34175d27a7ed4f8aec475cf2eb17a4f6dc5

Tx prefix hash: f8b55d3dd08be28c48034c305c8462d055015ace016af3b7fc9c35cc163078dd
Tx public key: 390acfdace000b38e0c1adcd1bdd5dca8aaed4b64abbbd89dc188346282ac4d6
Timestamp: 1710132491 Timestamp [UCT]: 2024-03-11 04:48:11 Age [y:d:h:m:s]: 00:262:10:16:17
Block: 975760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187874 RingCT/type: yes/0
Extra: 01390acfdace000b38e0c1adcd1bdd5dca8aaed4b64abbbd89dc188346282ac4d60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d418f8d9c76267d51d772971415ea6e994a9a95d15d5ae217b43571abc7aef 0.600000000000 1435733 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": 975770, "vin": [ { "gen": { "height": 975760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d418f8d9c76267d51d772971415ea6e994a9a95d15d5ae217b43571abc7aef" } } ], "extra": [ 1, 57, 10, 207, 218, 206, 0, 11, 56, 224, 193, 173, 205, 27, 221, 93, 202, 138, 174, 212, 182, 74, 187, 189, 137, 220, 24, 131, 70, 40, 42, 196, 214, 2, 17, 0, 0, 0, 5, 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