Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 988c147b53dcb3f4aa05569604009a7a3c3029700ea15d6ad83defd2c1eeb24b

Tx prefix hash: 4dbf4a00eb2c2a7655d0f2aa4ce3ae003decfc38629abfd38ab0aae62250d550
Tx public key: f4460bd241d233cecee2ea68f3006011d5d53950e567a76d68bbfedbfa123942
Timestamp: 1696103826 Timestamp [UCT]: 2023-09-30 19:57:06 Age [y:d:h:m:s]: 02:035:04:32:53
Block: 859651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544772 RingCT/type: yes/0
Extra: 01f4460bd241d233cecee2ea68f3006011d5d53950e567a76d68bbfedbfa12394202110000000633af99f4000000000000000000

1 output(s) for total of 0.870200686000 dcy

stealth address amount amount idx
00: c7f4af77249c28ad3b7a5133deffde1a42e3fe3925bd976d4bbf47727d7e1aad 0.870200686000 1313889 of 0

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": 859661, "vin": [ { "gen": { "height": 859651 } } ], "vout": [ { "amount": 870200686, "target": { "key": "c7f4af77249c28ad3b7a5133deffde1a42e3fe3925bd976d4bbf47727d7e1aad" } } ], "extra": [ 1, 244, 70, 11, 210, 65, 210, 51, 206, 206, 226, 234, 104, 243, 0, 96, 17, 213, 213, 57, 80, 229, 103, 167, 109, 104, 187, 254, 219, 250, 18, 57, 66, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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