Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68c091d27ec00cb83da270385853b8f2e5a7dda70e4a1faeb4db7bc93020543

Tx prefix hash: baa4fffcf22d57fbcf2958ce8d909d7601ee786d222bc89736a2706ad8d714c7
Tx public key: 22fe94aca1dc21d529a05e253ed23047a0a87e2dda40eef7d099fcf8c1a564cb
Timestamp: 1706749028 Timestamp [UCT]: 2024-02-01 00:57:08 Age [y:d:h:m:s]: 01:278:15:06:08
Block: 947678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457919 RingCT/type: yes/0
Extra: 0122fe94aca1dc21d529a05e253ed23047a0a87e2dda40eef7d099fcf8c1a564cb02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1109d8ae7ecc81ccdf4675ff0e9b4f50db6638d52eb26ca6e59d360a93aa10 0.600000000000 1406036 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": 947688, "vin": [ { "gen": { "height": 947678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1109d8ae7ecc81ccdf4675ff0e9b4f50db6638d52eb26ca6e59d360a93aa10" } } ], "extra": [ 1, 34, 254, 148, 172, 161, 220, 33, 213, 41, 160, 94, 37, 62, 210, 48, 71, 160, 168, 126, 45, 218, 64, 238, 247, 208, 153, 252, 248, 193, 165, 100, 203, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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