Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e175697066c163e56002a0dd1f261c8f1817386bb506cb6dc1e8f42bed3decb

Tx prefix hash: 46c7eff58afbf998617b506303b518dda80c83d4f169f19f8ad4d68d4679f4d6
Tx public key: 17711f1ddf53c8af487bddf0fb98793ba777f37d5d90901660b4a41be5b1bc9b
Timestamp: 1697283741 Timestamp [UCT]: 2023-10-14 11:42:21 Age [y:d:h:m:s]: 01:098:23:34:06
Block: 869428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331952 RingCT/type: yes/0
Extra: 0117711f1ddf53c8af487bddf0fb98793ba777f37d5d90901660b4a41be5b1bc9b02110000000833af99f4000000000000000000

1 output(s) for total of 0.807651767000 dcy

stealth address amount amount idx
00: ccf1ad61b2e4a7b53b279a11f4c2e7e52ab222646c6ea455a54a375f40ec3eec 0.807651767000 1324273 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": 869438, "vin": [ { "gen": { "height": 869428 } } ], "vout": [ { "amount": 807651767, "target": { "key": "ccf1ad61b2e4a7b53b279a11f4c2e7e52ab222646c6ea455a54a375f40ec3eec" } } ], "extra": [ 1, 23, 113, 31, 29, 223, 83, 200, 175, 72, 123, 221, 240, 251, 152, 121, 59, 167, 119, 243, 125, 93, 144, 144, 22, 96, 180, 164, 27, 229, 177, 188, 155, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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