Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3784afd2e1ba71bdaccc407d519fdd947cd9d19da4b7f220493f3e913a9c618e

Tx prefix hash: e20c9e03e1f3730e5156a5b425735100445a901912d71af942cb95b7e36872db
Tx public key: aedd940ee4e8fefe7632e44471d4f449336cd9e72fa7e9cf43b3d89e4ce7e884
Timestamp: 1733146695 Timestamp [UCT]: 2024-12-02 13:38:15 Age [y:d:h:m:s]: 00:124:03:53:26
Block: 1166441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88549 RingCT/type: yes/0
Extra: 01aedd940ee4e8fefe7632e44471d4f449336cd9e72fa7e9cf43b3d89e4ce7e884021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58eac57dcc55da39a657ad9e06cc75751063de398be28a505c77c632cb84ffd4 0.600000000000 1652128 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": 1166451, "vin": [ { "gen": { "height": 1166441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58eac57dcc55da39a657ad9e06cc75751063de398be28a505c77c632cb84ffd4" } } ], "extra": [ 1, 174, 221, 148, 14, 228, 232, 254, 254, 118, 50, 228, 68, 113, 212, 244, 73, 51, 108, 217, 231, 47, 167, 233, 207, 67, 179, 216, 158, 76, 231, 232, 132, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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