Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d201df3be0c588c6ceda191aaf23a9c8573a42c10da301636bd215cbc3e840

Tx prefix hash: 0d1793601a37a9642d082dd737e8f31d826ada7d49f5109fed68b46f20fcc2e3
Tx public key: 30852e8630bc97a45b283ec1530f7a3e10f5df64d5428ba8f7dd0d38182451f0
Timestamp: 1717378259 Timestamp [UCT]: 2024-06-03 01:30:59 Age [y:d:h:m:s]: 00:294:04:20:19
Block: 1035826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210227 RingCT/type: yes/0
Extra: 0130852e8630bc97a45b283ec1530f7a3e10f5df64d5428ba8f7dd0d38182451f0021100000002162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0039e718000aaeaba70ea11370120aa02496e4c51a35a1cfca2fa6a8034eed5d 0.600000000000 1504349 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": 1035836, "vin": [ { "gen": { "height": 1035826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0039e718000aaeaba70ea11370120aa02496e4c51a35a1cfca2fa6a8034eed5d" } } ], "extra": [ 1, 48, 133, 46, 134, 48, 188, 151, 164, 91, 40, 62, 193, 83, 15, 122, 62, 16, 245, 223, 100, 213, 66, 139, 168, 247, 221, 13, 56, 24, 36, 81, 240, 2, 17, 0, 0, 0, 2, 22, 38, 19, 170, 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