Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9345077e7b72b8257077b683231425d93a6003ecf04b8070a28def3cd64453a

Tx prefix hash: f7ebf61cfdcd7a48e31e67b4f060df4f6e3393f3dce9bb2d1b8eb326883f57a1
Tx public key: e7123cebcade084e277924fffdfe6d827445d1a0219323ebe16e040d2979c6b2
Timestamp: 1713854147 Timestamp [UCT]: 2024-04-23 06:35:47 Age [y:d:h:m:s]: 00:205:20:31:59
Block: 1006607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147352 RingCT/type: yes/0
Extra: 01e7123cebcade084e277924fffdfe6d827445d1a0219323ebe16e040d2979c6b202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394f4f418132fac0e4b5bb94b08bcf34c4eba0c7415354dbbac317f74c37bf9c 0.600000000000 1467685 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": 1006617, "vin": [ { "gen": { "height": 1006607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394f4f418132fac0e4b5bb94b08bcf34c4eba0c7415354dbbac317f74c37bf9c" } } ], "extra": [ 1, 231, 18, 60, 235, 202, 222, 8, 78, 39, 121, 36, 255, 253, 254, 109, 130, 116, 69, 209, 160, 33, 147, 35, 235, 225, 110, 4, 13, 41, 121, 198, 178, 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