Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d79c20f1f50d09d511759016acd444d398f2c3810eb597596c1f7e7aa6105cb

Tx prefix hash: 441bfb7377bfd8b62206bc720ddca972e15b8c2bc5828954d36780eea0047e22
Tx public key: 7a285a927e72baab36f044bcbabc873f6188f6663bc2d80d5e795ff3c33e1b92
Timestamp: 1726333659 Timestamp [UCT]: 2024-09-14 17:07:39 Age [y:d:h:m:s]: 01:046:14:42:57
Block: 1110063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291729 RingCT/type: yes/0
Extra: 017a285a927e72baab36f044bcbabc873f6188f6663bc2d80d5e795ff3c33e1b92021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f873daabd6e3db28dc47105e6f33aa461b1b6f3d1df5e99f39139bcfa009904b 0.600000000000 1588536 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": 1110073, "vin": [ { "gen": { "height": 1110063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f873daabd6e3db28dc47105e6f33aa461b1b6f3d1df5e99f39139bcfa009904b" } } ], "extra": [ 1, 122, 40, 90, 146, 126, 114, 186, 171, 54, 240, 68, 188, 186, 188, 135, 63, 97, 136, 246, 102, 59, 194, 216, 13, 94, 121, 95, 243, 195, 62, 27, 146, 2, 17, 0, 0, 0, 4, 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