Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c21424ab34063d103f35df66075d0862c9737519f5e5bbfae029c6db681b1fbe

Tx prefix hash: fc36170dacdaf30430dc5ba20caeb672f87219b5891b836d3d7c74abc3b214a4
Tx public key: fb8c649bb2b2b8ae2d4ba89807400af246f260f7bd52ebbc3af7f34450bd0630
Timestamp: 1712417517 Timestamp [UCT]: 2024-04-06 15:31:57 Age [y:d:h:m:s]: 01:011:15:58:22
Block: 994667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269329 RingCT/type: yes/0
Extra: 01fb8c649bb2b2b8ae2d4ba89807400af246f260f7bd52ebbc3af7f34450bd063002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0878bca469bb847e44944753e1d34e36a2de9a1c215854fdcfae8b2b3c8dfce 0.600000000000 1455071 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": 994677, "vin": [ { "gen": { "height": 994667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0878bca469bb847e44944753e1d34e36a2de9a1c215854fdcfae8b2b3c8dfce" } } ], "extra": [ 1, 251, 140, 100, 155, 178, 178, 184, 174, 45, 75, 168, 152, 7, 64, 10, 242, 70, 242, 96, 247, 189, 82, 235, 188, 58, 247, 243, 68, 80, 189, 6, 48, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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