Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f33fcd45cc7529d1cf1d74c7a03e31b407fedabf6475e3fa781ff265f5ceffa3

Tx prefix hash: eff4dd18aaf28ded67517f38bde3437ee9fe58ed8e029848236a30920890522a
Tx public key: 26e3e8494a821fbaa26adfc64b19c8e7022f72b57186f94aea5e8caeb9a2a921
Timestamp: 1581104438 Timestamp [UCT]: 2020-02-07 19:40:38 Age [y:d:h:m:s]: 05:271:04:56:27
Block: 60767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1343658 RingCT/type: yes/0
Extra: 0126e3e8494a821fbaa26adfc64b19c8e7022f72b57186f94aea5e8caeb9a2a92102110000001cd81c26c0000000000000000000

1 output(s) for total of 386.059746018000 dcy

stealth address amount amount idx
00: 79862d5aa2fd96027866671c279b33340e7945e09f6f2d48e2f9d57b184919c0 386.059746018000 111906 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": 60777, "vin": [ { "gen": { "height": 60767 } } ], "vout": [ { "amount": 386059746018, "target": { "key": "79862d5aa2fd96027866671c279b33340e7945e09f6f2d48e2f9d57b184919c0" } } ], "extra": [ 1, 38, 227, 232, 73, 74, 130, 31, 186, 162, 106, 223, 198, 75, 25, 200, 231, 2, 47, 114, 181, 113, 134, 249, 74, 234, 94, 140, 174, 185, 162, 169, 33, 2, 17, 0, 0, 0, 28, 216, 28, 38, 192, 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