Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d2511f58edb877999ec271511e764c7596462f1e2d80fd6bd56b5ee5d5f0d4

Tx prefix hash: d361b63aa52da382c1ed6cf2fc8b145b48fd7ddd3a9f759d7f55fbf748c50f1e
Tx public key: cf77051e5e2ceccdc19ada16888849877d96e15d440eb8e1db28191a8eef65b5
Timestamp: 1725627501 Timestamp [UCT]: 2024-09-06 12:58:21 Age [y:d:h:m:s]: 00:206:18:21:53
Block: 1104219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147604 RingCT/type: yes/0
Extra: 01cf77051e5e2ceccdc19ada16888849877d96e15d440eb8e1db28191a8eef65b502110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f711ee1237766c3cfde823e56274f9c3fdc06dada868ee6c16550c7c753cdcc 0.600000000000 1581298 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": 1104229, "vin": [ { "gen": { "height": 1104219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f711ee1237766c3cfde823e56274f9c3fdc06dada868ee6c16550c7c753cdcc" } } ], "extra": [ 1, 207, 119, 5, 30, 94, 44, 236, 205, 193, 154, 218, 22, 136, 136, 73, 135, 125, 150, 225, 93, 68, 14, 184, 225, 219, 40, 25, 26, 142, 239, 101, 181, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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